PUCCH based beam failure recovery procedure

ABSTRACT

A wireless device receives one or more messages comprising one or more configuration parameters indicating: one or more reference signals for a beam failure detection procedure; and a discontinuous reception (DRX) configuration for controlling transitions between a DRX inactive state and a DRX active state. The beam failure detection procedure is performed based on measurements of the one or more reference signals. A first value of a counter is determined based on detecting at least one beam failure instance during the DRX active state. A transition from the DRX active state to the DRX inactive state is made based on the DRX configuration. The beam failure detection procedure is stopped in response to the transitioning. The beam failure detection procedure continues with the first value of the counter after transitioning from the DRX inactive state to the DRX active state.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/438,811, filed Jun. 12, 2019, issued as U.S. Pat. No. 11,277,302,which claims the benefit of U.S. Provisional Application No. 62/688,327,filed Jun. 21, 2018, each of which are hereby incorporated by referencein their entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example transmission time or receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 16A and FIG. 16B are examples of downlink beam failure scenario asper an aspect of an embodiment of the present disclosure.

FIG. 17 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 18 is an example of a request configuration for beam failurerecovery procedure as per an aspect of an embodiment of the presentdisclosure.

FIG. 19 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 20 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 21 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 22 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 23 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 24 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 25 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 26 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 27 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 28 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 29 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 30 is an example of downlink beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 31 is a flow chart of an aspect of an example embodiment of thepresent disclosure.

FIG. 32 is a flow chart of an aspect of an example embodiment of thepresent disclosure.

FIG. 33 is a flow chart of an aspect of an example embodiment of thepresent disclosure.

FIG. 34 is a flow chart of an aspect of an example embodiment of thepresent disclosure.

FIG. 35 is a flow chart of an aspect of an example embodiment of thepresent disclosure.

FIG. 36 is a flow chart of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation of beamfailure recovery procedure. Embodiments of the technology disclosedherein may be employed in the technical field of multicarriercommunication systems. More particularly, the embodiments of thetechnology disclosed herein may relate to beam failure recoveryprocedure in a multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

-   -   3GPP 3rd Generation Partnership Project    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASIC Application-Specific Integrated Circuit    -   BA Bandwidth Adaptation    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BPSK Binary Phase Shift Keying    -   BWP Bandwidth Part    -   BSR Buffer Status Report    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control CHannel    -   CDMA Code Division Multiple Access    -   CN Core Network    -   CP Cyclic Prefix    -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex    -   C-RNTI Cell-Radio Network Temporary Identifier    -   CS Configured Scheduling    -   CSI Channel State Information    -   CSI-RS Channel State Information-Reference Signal    -   CQI Channel Quality Indicator    -   CSS Common Search Space    -   CU Central Unit    -   DC Dual Connectivity    -   DCCH Dedicated Control Channel    -   DCI Downlink Control Information    -   DL Downlink    -   DL-SCH Downlink Shared CHannel    -   DM-RS DeModulation Reference Signal    -   DRB Data Radio Bearer    -   DRX Discontinuous Reception    -   DTCH Dedicated Traffic Channel    -   DU Distributed Unit    -   EPC Evolved Packet Core    -   E-UTRA Evolved UMTS Terrestrial Radio Access    -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FPGA Field Programmable Gate Arrays    -   F1-C F1-Control plane    -   F1-U F1-User plane    -   gNB next generation Node B    -   HARQ Hybrid Automatic Repeat reQuest    -   HDL Hardware Description Languages    -   IE Information Element    -   IP Internet Protocol    -   LCID Logical Channel Identifier    -   LTE Long Term Evolution    -   MAC Media Access Control    -   MCG Master Cell Group    -   MCS Modulation and Coding Scheme    -   MeNB Master evolved Node B    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MN Master Node    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NG CP Next Generation Control Plane    -   NGC Next Generation Core    -   NG-C NG-Control plane    -   ng-eNB next generation evolved Node B    -   NG-U NG-User plane    -   NR New Radio    -   NR MAC New Radio MAC    -   NR PDCP New Radio PDCP    -   NR PHY New Radio PHYsical    -   NR RLC New Radio RLC    -   NR RRC New Radio RRC    -   NSSAI Network Slice Selection Assistance Information    -   O&M Operation and Maintenance    -   OFDM orthogonal Frequency Division Multiplexing    -   PBCH Physical Broadcast CHannel    -   PCC Primary Component Carrier    -   PCCH Paging Control CHannel    -   PCell Primary Cell    -   PCH Paging CHannel    -   PDCCH Physical Downlink Control CHannel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared CHannel    -   PDU Protocol Data Unit    -   PHICH Physical HARQ Indicator CHannel    -   PHY PHYsical    -   PLMN Public Land Mobile Network    -   PMI Precoding Matrix Indicator    -   PRACH Physical Random Access CHannel    -   PRB Physical Resource Block    -   PSCell Primary Secondary Cell    -   PSS Primary Synchronization Signal    -   pTAG primary Timing Advance Group    -   PT-RS Phase Tracking Reference Signal    -   PUCCH Physical Uplink Control CHannel    -   PUSCH Physical Uplink Shared CHannel    -   QAM Quadrature Amplitude Modulation    -   QFI Quality of Service Indicator    -   QoS Quality of Service    -   QPSK Quadrature Phase Shift Keying    -   RA Random Access    -   RACH Random Access CHannel    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RA-RNTI Random Access-Radio Network Temporary Identifier    -   RB Resource Blocks    -   RBG Resource Block Groups    -   RI Rank indicator    -   RLC Radio Link Control    -   RRC Radio Resource Control    -   RS Reference Signal    -   RSRP Reference Signal Received Power    -   SCC Secondary Component Carrier    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SC-FDMA Single Carrier-Frequency Division Multiple Access    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SeNB Secondary evolved Node B    -   SFN System Frame Number    -   S-GW Serving GateWay    -   SI System Information    -   SIB System Information Block    -   SMF Session Management Function    -   SN Secondary Node    -   SpCell Special Cell    -   SR Scheduling Request    -   SRB Signaling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   sTAG secondary Timing Advance Group    -   TA Timing Advance    -   TAG Timing Advance Group    -   TAI Tracking Area Identifier    -   TAT Time Alignment Timer    -   TB Transport Block    -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier    -   TDD Time Division Duplex    -   TDMA Time Division Multiple Access    -   TTI Transmission Time Interval    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UL-SCH Uplink Shared CHannel    -   UPF User Plane Function    -   UPGW User Plane Gateway    -   VHDL VHSIC Hardware Description Language    -   Xn-C Xn-Control plane    -   Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CodeDivision Multiple Access (CDMA), Orthogonal Frequency Division MultipleAccess (OFDMA), Time Division Multiple Access (TDMA), Wavelettechnologies, and/or the like. Hybrid transmission mechanisms such asTDMA/CDMA, and OFDM/CDMA may also be employed. Various modulationschemes may be applied for signal transmission in the physical layer.Examples of modulation schemes include, but are not limited to: phase,amplitude, code, a combination of these, and/or the like. An exampleradio transmission method may implement Quadrature Amplitude Modulation(QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase ShiftKeying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 120C, 120D), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface.

A gNB or an ng-eNB may host functions such as radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, dual connectivity or tight interworking betweenNR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide functions such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer or warning message transmission.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TBs)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCD). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCD for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCD associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A,FIG. 7B, FIG. 8 , and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel. A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MC S)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 andSSB/PBCH are spatially quasi co-located and resource elements associatedwith the downlink CSI-RS 522 are the outside of PRBs configured forSSB/PBCH.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example transmission time and receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers, in case ofcarrier aggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6 , asubframe may be divided into two equally sized slots 603 with 0.5 msduration. For example, 10 subframes may be available for downlinktransmission and 10 subframes may be available for uplink transmissionsin a 10 ms interval. Uplink and downlink transmissions may be separatedin the frequency domain. Slot(s) may include a plurality of OFDM symbols604. The number of OFDM symbols 604 in a slot 605 may depend on thecyclic prefix length. For example, a slot may be 14 OFDM symbols for thesame subcarrier spacing of up to 480 kHz with normal CP. A slot may be12 OFDM symbols for the same subcarrier spacing of 60 kHz with extendedCP. A slot may contain downlink, uplink, or a downlink part and anuplink part and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8 , a resource block 806 may comprise 12 subcarriers.In an example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RSs. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel. Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCL-ed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base statin maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice; a master base station may (e.g. based on received measurementreports, traffic conditions, and/or bearer types) may decide to requesta secondary base station to provide additional resources (e.g. servingcells) for a wireless device; upon receiving a request from a masterbase station, a secondary base station may create/modify a containerthat may result in configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so); for a UE capability coordination, a masterbase station may provide (a part of) an AS configuration and UEcapabilities to a secondary base station; a master base station and asecondary base station may exchange information about a UE configurationby employing of RRC containers (inter-node messages) carried via Xnmessages; a secondary base station may initiate a reconfiguration of thesecondary base station existing serving cells (e.g. PUCCH towards thesecondary base station); a secondary base station may decide which cellis a PSCell within a SCG; a master base station may or may not changecontent of RRC configurations provided by a secondary base station; incase of a SCG addition and/or a SCG SCell addition, a master basestation may provide recent (or the latest) measurement results for SCGcell(s); a master base station and secondary base stations may receiveinformation of SFN and/or subframe offset of each other from OAM and/orvia an Xn interface, (e.g. for a purpose of DRX alignment and/oridentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of a cell as for CA, except for a SFN acquired from aMIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg 1 1220 transmissions, one ormore Msg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery procedure and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery procedure,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery procedureassociated with at least one of SS blocks and/or CSI-RSs. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery procedure.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs,the UE may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS. A UE may transmit, to a basestation, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery procedure. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For beam failurerecovery procedure, a base station may configure a UE with a differenttime window (e.g., bfr-ResponseWindow) to monitor response on beamfailure recovery procedure. For example, a UE may start a time window(e.g., ra-ResponseWindow or bfr-Response Window) at a start of a firstPDCCH occasion after a fixed duration of one or more symbols from an endof a preamble transmission. If a UE transmits multiple preambles, the UEmay start a time window at a start of a first PDCCH occasion after afixed duration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery procedure identified by a C-RNTI while a timer fora time window is running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery procedure, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. gNB 120A or 120B) may comprise a base station central unit (CU)(e.g. gNB-CU 1420A or 1420B) and at least one base station distributedunit (DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g. CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. In an example, an Xn interface may be configuredbetween base station CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may communicate with a wireless device via a wireless networkemploying one or more new radio technologies. The one or more radiotechnologies may comprise at least one of: multiple technologies relatedto physical layer; multiple technologies related to medium accesscontrol layer; and/or multiple technologies related to radio resourcecontrol layer. Example embodiments of enhancing the one or more radiotechnologies may improve performance of a wireless network. Exampleembodiments may increase the system throughput, or data rate oftransmission. Example embodiments may reduce battery consumption of awireless device. Example embodiments may improve latency of datatransmission between a gNB and a wireless device. Example embodimentsmay improve network coverage of a wireless network. Example embodimentsmay improve transmission efficiency of a wireless network.

Example of Carrier Aggregation

In a carrier aggregation (CA), two or more component carriers (CCs) maybe aggregated. A wireless device may simultaneously receive or transmiton one or more CCs depending on capabilities of the wireless device. Inan example, the CA may be supported for contiguous CCs. In an example,the CA may be supported for non-contiguous CCs.

When configured with a CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing a NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may be referredto as a primary cell (PCell). In an example, a gNB may transmit, to awireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells),depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell for an efficientbattery consumption. When a wireless device is configured with one ormore SCells, a gNB may activate or deactivate at least one of the one ormore SCells. Upon configuration of an SCell, the SCell may bedeactivated.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a base station may transmit, to a wireless device, one ormore messages comprising an sCellDeactivationTimer timer. In an example,a wireless device may deactivate an SCell in response to an expiry ofthe sCellDeactivationTimer timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising SRS transmissions on the SCell, CQI/PMI/RI/CRIreporting for the SCell on a PCell, PDCCH monitoring on the SCell, PDCCHmonitoring for the SCell on the PCell, and/or PUCCH transmissions on theSCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart an sCellDeactivationTimer timer associatedwith the SCell. The wireless device may start the sCellDeactivationTimertimer in the slot when the SCell Activation/Deactivation MAC CE has beenreceived. In an example, in response to the activating the SCell, thewireless device may (re-)initialize one or more suspended configureduplink grants of a configured grant Type 1 associated with the SCellaccording to a stored configuration. In an example, in response to theactivating the SCell, the wireless device may trigger PHR.

In an example, when a wireless device receives an SCellActivation/Deactivation MAC CE deactivating an activated SCell, thewireless device may deactivate the activated SCell.

In an example, when an sCellDeactivationTimer timer associated with anactivated SCell expires, the wireless device may deactivate theactivated SCell. In response to the deactivating the activated SCell,the wireless device may stop the sCellDeactivationTimer timer associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may clear one or moreconfigured downlink assignments and/or one or more configured uplinkgrant Type 2 associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay further suspend one or more configured uplink grant Type 1associated with the activated SCell. The wireless device may flush HARQbuffers associated with the activated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising transmitting SRS on the SCell, reportingCQI/PMI/RI/CRI for the SCell on a PCell, transmitting on UL-SCH on theSCell, transmitting on RACH on the SCell, monitoring at least one firstPDCCH on the SCell, monitoring at least one second PDCCH for the SCellon the PCell, transmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart an sCellDeactivationTimer timer associated with theactivated SCell. In an example, when at least one second PDCCH on aserving cell (e.g. a PCell or an SCell configured with PUCCH, i.e. PUCCHSCell) scheduling the activated SCell indicates an uplink grant or adownlink assignment for the activated SCell, a wireless device mayrestart an sCellDeactivationTimer timer associated with the activatedSCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

Example Bandwidth Parts (BWPs)

A base station (gNB) may configure a wireless device (UE) with uplink(UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidthadaptation (BA) on a PCell. If carrier aggregation is configured, thegNB may configure the UE with at least DL BWP(s) (i.e. there may be noUL BWPS in the UL) to enable BA on an SCell. For the PCell, a firstinitial BWP may be a first BWP used for initial access. For the SCell, asecond initial BWP is a second BWP configured for the UE to firstoperate at the SCell when the SCell is activated.

In paired spectrum (e.g. FDD), a first DL and a first UL can switch BWPindependently. In unpaired spectrum (e.g. TDD), a second DL and a secondUL switch BWP simultaneously. Switching between configured BWPs mayhappen by means of a DCI or an inactivity timer. When the inactivitytimer is configured for a serving cell, an expiry of the inactivitytimer associated to that cell may switch an active BWP to a default BWP.The default BWP may be configured by the network.

In an example, for FDD systems, when configured with BA, one UL BWP foreach uplink carrier and one DL BWP may be active at a time in an activeserving cell. In an example, for TDD systems, one DL/UL BWP pair may beactive at a time in an active serving cell. Operating on the one UL BWPand the one DL BWP (or the one DL/UL pair) may enable reasonable UEbattery consumption. BWPs other than the one UL BWP and the one DL BWPthat the UE may be configured with may be deactivated. On deactivatedBWPs, the UE may not monitor PDCCH, may not transmit on PUCCH, PRACH andUL-SCH.

In an example, a Serving Cell may be configured with at most a firstnumber (e.g., four) BWPs. In an example, for an activated Serving Cell,there may be one active BWP at any point in time.

In an example, a BWP switching for a Serving Cell may be used toactivate an inactive BWP and deactivate an active BWP at a time. In anexample, the BWP switching may be controlled by a PDCCH indicating adownlink assignment or an uplink grant. In an example, the BWP switchingmay be controlled by an inactivity timer (e.g.bandwidthpartInactivityTimer). In an example, the BWP switching may becontrolled by a MAC entity in response to initiating a Random Accessprocedure. Upon addition of SpCell or activation of an SCell, one BWPmay be initially active without receiving a PDCCH indicating a downlinkassignment or an uplink grant. The active BWP for a Serving Cell may beindicated by RRC and/or PDCCH. In an example, for unpaired spectrum, aDL BWP may be paired with a UL BWP, and BWP switching may be common forboth UL and DL.

In an example, a MAC entity may apply normal operations on an active BWPfor an activated Serving Cell configured with a BWP including:transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH;transmitting PUCCH; receiving DL-SCH; (re-) initializing any suspendedconfigured uplink grants of configured grant Type 1 according to astored configuration, if any, and to start in a symbol based on someprocedure.

In an example, on an inactive BWP for each activated Serving Cellconfigured with a BWP, a MAC entity may not transmit on UL-SCH; may nottransmit on RACH; may not monitor a PDCCH; may not transmit PUCCH; maynot transmit SRS, may not receive DL-SCH; may clear any configureddownlink assignment and configured uplink grant of configured grant Type2; may suspend any configured uplink grant of configured Type 1.

In an example, upon initiation of a Random Access procedure, if PRACHresources are configured for an active UL BWP, a MAC entity may performthe Random Access procedure on an active DL BWP and the active UL BWP.In an example, upon initiation of a Random Access procedure, if PRACHresources are not configured for an active UL BWP, a MAC entity mayswitch to an initial DL BWP and an initial UL BWP. In response to theswitching, the MAC entity may perform the Random Access procedure on theinitial DL BWP and the initial UL BWP.

In an example, if a MAC entity receives a PDCCH for a BWP switching of aserving cell while a Random Access procedure associated with thisserving cell is not ongoing, a UE may perform the BWP switching to a BWPindicated by the PDCCH.

In an example, if a MAC entity receives a PDCCH for a BWP switchingwhile a Random Access procedure is ongoing in the MAC entity, it may beup to UE implementation whether to switch BWP or ignore the PDCCH forthe BWP switching. In an example, if the MAC entity decides to performthe BWP switching, the MAC entity may stop the ongoing Random Accessprocedure and initiate a second Random Access procedure on a newactivated BWP. In an example, if the MAC decides to ignore the PDCCH forthe BWP switching, the MAC entity may continue with the ongoing RandomAccess procedure on the active BWP.

In an example, if a MAC entity receives a PDCCH for a BWP switchingaddressed to a C-RNTI for a successful completion of a Random Accessprocedure, a UE may perform the BWP switching to a BWP indicated by thePDCCH.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if a PDCCHaddressed to C-RNTI or CS-RNTI indicating downlink assignment or uplinkgrant is received on the active BWP: if there is not an ongoing randomaccess procedure associated with the activated Serving Cell, the MACentity may start or restart the BWP-InactivityTimer associated with theactive DL BWP.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if aMAC-PDU is transmitted in a configured uplink grant or received in aconfigured downlink assignment; if there is not an ongoing random accessprocedure associated with the activated Serving Cell, the MAC entity maystart or restart the BWP-InactivityTimer associated with the active DLBWP.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if a PDCCHaddressed to C-RNTI or CS-RNTI indicating downlink assignment or uplinkgrant is received on the active BWP; or if a MAC-PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment:if an ongoing random access procedure associated with the activatedServing Cell is successfully completed in response to receiving thePDCCH addressed to a C-RNTI, the MAC entity may start or restart theBWP-InactivityTimer associated with the active DL BWP.

In an example, if a BWP-InactivityTimer is configured, for an activatedServing Cell, if a Default-DL-BWP is configured, and an active DL BWP isnot a BWP indicated by the Default-DL-BWP; or if the Default-DL-BWP isnot configured, and the active DL BWP is not the initial BWP: if a PDCCHfor a BWP switching is received on the active DL BWP, a MAC entity maystart or restart the BWP-InactivityTimer associated with the active DLBWP in response to switching the active BWP.

In an example, if BWP-InactivityTimer is configured, for an activatedServing Cell, if the Default-DL-BWP is configured, and the active DL BWPis not the BWP indicated by the Default-DL-BWP; or if the Default-DL-BWPis not configured, and the active DL BWP is not the initial BWP: ifRandom Access procedure is initiated, the MAC entity may stop theBWP-InactivityTimer associated with the active DL BWP of the activatedServing Cell. If the activated Serving Cell is an SCell (other than aPSCell), the MAC entity may stop a second BWP-InactivityTimer associatedwith a second active DL BWP of an SpCell.

In an example, if BWP-InactivityTimer is configured, for an activatedServing Cell, if the Default-DL-BWP is configured, and the active DL BWPis not the BWP indicated by the Default-DL-BWP; or if the Default-DL-BWPis not configured, and the active DL BWP is not the initial BWP: ifBWP-InactivityTimer associated with the active DL BWP expires: if theDefault-DL-BWP is configured, the MAC entity may perform BWP switchingto a BWP indicated by the Default-DL-BWP. Otherwise, the MAC entity mayperform BWP switching to the initial DL BWP.

In an example, a UE may be configured for operation in bandwidth parts(BWPs) of a serving cell. In an example, the UE may be configured byhigher layers for the serving cell a set of (e.g., at most four)bandwidth parts (BWPs) for receptions by the UE (e.g., DL BWP set) in aDL bandwidth by parameter DL-BWP. In an example, the UE may beconfigured with a set of (e.g., at most four) BWPs for transmissions bythe UE (e.g., UL BWP set) in an UL bandwidth by parameter UL-BWP for theserving cell.

In an example, an initial active DL BWP may be defined, for example, bya location and number of contiguous PRBs, a subcarrier spacing, and acyclic prefix, for the control resource set for Type0-PDCCH commonsearch space. In an example, for operation on a primary cell, a UE maybe provided by higher layer with a parameter initial-UL-BWP, an initialactive UL BWP for a random access procedure.

In an example, if a UE has a dedicated BWP configuration, the UE may beprovided by higher layer parameter Active-BWP-DL-Pcell a first active DLBWP for receptions. If a UE has a dedicated BWP configuration, the UEmay be provided by higher layer parameter Active-BWP-UL-Pcell a firstactive UL BWP for transmissions on a primary cell.

In an example, for a DL BWP or an UL BWP in a set of DL BWPs or UL BWPs,respectively, the UE may be configured with the following parameters forthe serving cell: a subcarrier spacing provided by higher layerparameter DL-BWP-mu or UL-BWP-mu; a cyclic prefix provided by higherlayer parameter DL-BWP-CP or UL-BWP-CP; a PRB offset with respect to thePRB determined by higher layer parameters offset-pointA-low-scs andref-scs and a number of contiguous PRBs provided by higher layerparameter DL-BWP-BW or UL-BWP-BW; an index in the set of DL BWPs or ULBWPs by respective higher layer parameters DL-BWP-index or UL-BWP-index;a DCI format 1_0 or DCI format 1_1 detection to a PDSCH reception timingvalues by higher layer parameter DL-data-time-domain; a PDSCH receptionto a HARQ-ACK transmission timing values by higher layer parameterDL-data-DL-acknowledgement; and a DCI 0_0 or DCI 0_1 detection to aPUSCH transmission timing values by higher layer parameterUL-data-time-domain;

In an example, for an unpaired spectrum operation, a DL BWP from a setof configured DL BWPs with index provided by higher layer parameterDL-BWP-index may be paired with an UL BWP from a set of configured ULBWPs with index provided by higher layer parameter UL-BWP-index when theDL BWP index and the UL BWP index are equal. For unpaired spectrumoperation, a UE may not be expected to receive a configuration where thecenter frequency for a DL BWP is different than the center frequency foran UL BWP when the DL-BWP-index of the DL BWP is equal to theUL-BWP-index of the UL BWP.

In an example, for a DL BWP in a set of DL BWPs on the primary cell, aUE may be configured control resource sets for every type of commonsearch space and for UE-specific search space. In an example, the UE maynot be expected to be configured without a common search space on thePCell, or on the PSCell, in the active DL BWP. In an example, for an ULBWP in a set of UL BWPs, the UE may be configured resource sets forPUCCH transmissions. In an example, a UE may receive PDCCH and PDSCH ina DL BWP according to a configured subcarrier spacing and CP length forthe DL BWP. A UE may transmit PUCCH and PUSCH in an UL BWP according toa configured subcarrier spacing and CP length for the UL BWP.

In an example, if a bandwidth part indicator field is configured in DCIformat 1_1, the bandwidth part indicator field value may indicate theactive DL BWP, from the configured DL BWP set, for DL receptions. In anexample, if a bandwidth part indicator field is configured in DCI format0_1, the bandwidth part indicator field value may indicate the active ULBWP, from the configured UL BWP set, for UL transmissions. In anexample, for the primary cell, a UE may be provided by higher layerparameter Default-DL-BWP, a default DL BWP among the configured DL BWPs.In an example, if a UE is not provided a default DL BWP by higher layerparameter Default-DL-BWP, the default BWP may be the initial active DLBWP.

In an example, a UE may be expected to detect a DCI format 0_1indicating active UL BWP change, or a DCI format 1_1 indicating activeDL BWP change, only if a corresponding PDCCH is received within first 3symbols of a slot.

In an example, for a primary cell, a UE may be provided by a higherlayer parameter Default-DL-BWP a default DL BWP among the configured DLBWPs. If a UE is not provided a default DL BWP by the higher layerparameter Default-DL-BWP, the default DL BWP is the initial active DLBWP.

In an example, a UE may be provided by higher layer parameterBWP-InactivityTimer, a timer value for the primary cell. If configured,the UE may increment the timer, if running, every interval of 1millisecond for frequency range 1 or every 0.5 milliseconds forfrequency range 2 if the UE may not detect a DCI format 1_1 for pairedspectrum operation or if the UE may not detect a DCI format 1_1 or DCIformat 0_1 for unpaired spectrum operation during the interval.

In an example, if a UE is configured for a secondary cell with higherlayer parameter Default-DL-BWP indicating a default DL BWP among theconfigured DL BWPs and the UE is configured with higher layer parameterBWP-InactivityTimer indicating a timer value, the UE procedures on thesecondary cell may be same as on the primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a UE is configured by higher layer parameterActive-BWP-DL-SCell a first active DL BWP and by higher layer parameterActive-BWP-UL-SCell a first active UL BWP on a secondary cell orcarrier, the UE may use the indicated DL BWP and the indicated UL BWP onthe secondary cell as the respective first active DL BWP and firstactive UL BWP on the secondary cell or carrier.

In an example, for paired spectrum operation, a UE may not be expectedto transmit HARQ-ACK on a PUCCH resource indicated by a DCI format 1_0or a DCI format 1_1 if the UE changes its active UL BWP on a PCellbetween a time of a detection of the DCI format 1_0 or the DCI format1_1 and a time of a corresponding HARQ-ACK transmission on the PUCCH.

In an example, a UE may not be expected to monitor PDCCH when the UEperforms RRM measurements over a bandwidth that is not within the activeDL BWP for the UE.

Example Downlink Control Information (DCI)

In an example, a gNB may transmit a DCI via a PDCCH for at least one of:scheduling assignment/grant; slot format notification; pre-emptionindication; and/or power-control commends. More specifically, the DCImay comprise at least one of: identifier of a DCI format; downlinkscheduling assignment(s); uplink scheduling grant(s); slot formatindicator; pre-emption indication; power-control for PUCCH/PUSCH; and/orpower-control for SRS.

In an example, a downlink scheduling assignment DCI may compriseparameters indicating at least one of: identifier of a DCI format; PDSCHresource indication; transport format; HARQ information; controlinformation related to multiple antenna schemes; and/or a command forpower control of the PUCCH.

In an example, an uplink scheduling grant DCI may comprise parametersindicating at least one of: identifier of a DCI format; PUSCH resourceindication; transport format; HARQ related information; and/or a powercontrol command of the PUSCH.

In an example, different types of control information may correspond todifferent DCI message sizes. For example, supporting multiple beamsand/or spatial multiplexing in the spatial domain and noncontiguousallocation of RBs in the frequency domain may require a largerscheduling message, in comparison with an uplink grant allowing forfrequency-contiguous allocation. DCI may be categorized into differentDCI formats, where a format corresponds to a certain message size and/orusage.

In an example, a wireless device may monitor one or more PDCCH fordetecting one or more DCI with one or more DCI format, in common searchspace or wireless device-specific search space. In an example, awireless device may monitor PDCCH with a limited set of DCI format, tosave power consumption. The more DCI format to be detected, the morepower be consumed at the wireless device.

In an example, the information in the DCI formats for downlinkscheduling may comprise at least one of: identifier of a DCI format;carrier indicator; RB allocation; time resource allocation; bandwidthpart indicator; HARQ process number; one or more MCS; one or more NDI;one or more RV; MIMO related information; Downlink assignment index(DAI); TPC for PUCCH; SRS request; and padding if necessary. In anexample, the MIMO related information may comprise at least one of: PMI;precoding information; transport block swap flag; power offset betweenPDSCH and reference signal; reference-signal scrambling sequence; numberof layers; and/or antenna ports for the transmission; and/orTransmission Configuration Indication (TCI).

In an example, the information in the DCI formats used for uplinkscheduling may comprise at least one of: an identifier of a DCI format;carrier indicator; bandwidth part indication; resource allocation type;RB allocation; time resource allocation; MCS; NDI; Phase rotation of theuplink DMRS; precoding information; CSI request; SRS request; Uplinkindex/DAI; TPC for PUSCH; and/or padding if necessary.

In an example, a gNB may perform CRC scrambling for a DCI, beforetransmitting the DCI via a PDCCH. The gNB may perform CRC scrambling bybinarily adding multiple bits of at least one wireless device identifier(e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SPCSI C-RNTI, or TPC-SRS-RNTI) on the CRC bits of the DCI. The wirelessdevice may check the CRC bits of the DCI, when detecting the DCI. Thewireless device may receive the DCI when the CRC is scrambled by asequence of bits that is the same as the at least one wireless deviceidentifier.

In an example, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets(coresets). A gNB may transmit one or more RRC message comprisingconfiguration parameters of one or more coresets. A coreset may compriseat least one of: a first OFDM symbol; a number of consecutive OFDMsymbols; a set of resource blocks; a CCE-to-REG mapping. In an example,a gNB may transmit a PDCCH in a dedicated coreset for particularpurpose, for example, for beam failure recovery confirmation.

In an example, a wireless device may monitor PDCCH for detecting DCI inone or more configured coresets, to reduce the power consumption.

Example of a BFR Procedure.

A gNB and/or a wireless device may have multiple antenna, to support atransmission with high data rate in a NR system. When configured withmultiple antennas, a wireless device may perform one or more beammanagement procedures, as shown in FIG. 9B.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs, and/or one or more SSBs. In a beam management procedure, awireless device may measure a channel quality of a beam pair link. Thebeam pair link may comprise a transmitting beam from a gNB and areceiving beam at the wireless device. When configured with multiplebeams associated with multiple CSI-RSs or SSBs, a wireless device maymeasure the multiple beam pair links between the gNB and the wirelessdevice.

In an example, a wireless device may transmit one or more beammanagement reports to a gNB. In a beam management report, the wirelessdevice may indicate one or more beam pair quality parameters, comprisingat least, one or more beam identifications; RSRP; PMI/CQI/RI of at leasta subset of configured multiple beams.

In an example, a gNB and/or a wireless device may perform a downlinkbeam management procedure on one or multiple Transmission and ReceivingPoint (TRPs), as shown in FIG. 9B. Based on a wireless device's beammanagement report, a gNB may transmit to the wireless device a signalindicating that a new beam pair link is a serving beam. The gNB maytransmit PDCCH and PDSCH to the wireless device using the serving beam.

In an example, a wireless device or a gNB may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery (BFR) procedure, e.g., when at least a beam failure occurs. Inan example, a beam failure may occur when quality of beam pair link(s)of at least one PDCCH falls below a threshold. The threshold may be aRSRP value (e.g., −140 dbm, −110 dbm) or a SINR value (e.g., −3 dB, −1dB), which may be configured in a RRC message.

FIG. 16A shows example of a first beam failure scenario. In the example,a gNB may transmit a PDCCH from a transmission (Tx) beam to a receiving(Rx) beam of a wireless device from a TRP. When the PDCCH on the beampair link (between the Tx beam of the gNB and the Rx beam of thewireless device) have a lower-than-threshold RSRP/SINR value due to thebeam pair link being blocked (e.g., by a moving car or a building), thegNB and the wireless device may start a beam failure recovery procedureon the TRP.

FIG. 16B shows example of a second beam failure scenario. In theexample, the gNB may transmit a PDCCH from a beam to a wireless devicefrom a first TRP. When the PDCCH on the beam is blocked, the gNB and thewireless device may start a beam failure recovery procedure on a newbeam on a second TRP.

In an example, a wireless device may measure quality of beam pair linkusing one or more RSs. The one or more RSs may be one or more SSBs, orone or more CSI-RS resources. A CSI-RS resource may be identified by aCSI-RS resource index (CRI). In an example, quality of beam pair linkmay be defined as a RSRP value, or a reference signal received quality(e.g. RSRQ) value, and/or a CSI (e.g., SINR) value measured on RSresources. In an example, a gNB may indicate whether an RS resource,used for measuring beam pair link quality, is QCLed (Quasi-Co-Located)with DM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH maybe called QCLed when the channel characteristics from a transmission onan RS to a wireless device, and that from a transmission on a PDCCH tothe wireless device, are similar or same under a configured criterion.In an example, The RS resource and the DM-RSs of the PDCCH may be calledQCLed when doppler shift and/or doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are same.

In an example, a wireless device may monitor PDCCH on M beam (e.g. 2, 4,8) pair links simultaneously, where M≥1 and the value of M may depend atleast on capability of the wireless device. In an example, monitoring aPDCCH may comprise detecting a DCI via the PDCCH transmitted on commonsearch spaces and/or wireless device specific search spaces. In anexample, monitoring multiple beam pair links may increase robustnessagainst beam pair link blocking. In an example, a gNB may transmit oneor more messages comprising parameters indicating a wireless device tomonitor PDCCH on different beam pair link(s) in different OFDM symbols.

In an example, a gNB may transmit one or more RRC messages or MAC CEscomprising parameters indicating Rx beam setting of a wireless devicefor monitoring PDCCH on multiple beam pair links. A gNB may transmit anindication of spatial QCL between an DL RS antenna port(s) and DL RSantenna port(s) for demodulation of DL control channel. In an example,the indication may be a parameter in a MAC CE, or a RRC message, or aDCI, and/or combination of these signaling.

In an example, for reception of data packet on a PDSCH, a gNB mayindicate spatial QCL parameters between DL RS antenna port(s) and DM-RSantenna port(s) of DL data channel. A gNB may transmit DCI comprisingparameters indicating the RS antenna port(s) QCL-ed with DM-RS antennaport(s).

In an example, when a gNB transmits a signal indicating QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may measure a beampair link quality based on CSI-RSs QCLed with DM-RS for PDCCH. In anexample, when multiple contiguous beam failures occur, the wirelessdevice may start a BFR procedure.

In an example, a wireless device transmits a BFR signal on an uplinkphysical channel to a gNB when starting a BFR procedure. The gNB maytransmit a DCI via a PDCCH in a coreset in response to receiving the BFRsignal on the uplink physical channel. The wireless may consider the BFRprocedure successfully completed when receiving the DCI via the PDCCH inthe coreset.

In an example, a gNB may transmit one or more messages comprisingconfiguration parameters of an uplink physical channel or signal fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (BFR-PUCCH); and/or a contention-basedPRACH resource (CF-PRACH). Combinations of these candidatesignal/channels may be configured by the gNB. In an example, whenconfigured with multiple resources for a BFR signal, a wireless devicemay autonomously select a first resource for transmitting the BFRsignal. In an example, when configured with a BFR-PRACH resource, aBFR-PUCCH resource, and a CF-PRACH resource, the wireless device mayselect the BFR-PRACH resource for transmitting the BFR signal. In anexample, when configured with a BFR-PRACH resource, a BFR-PUCCHresource, and a CF-PRACH resource, the gNB may transmit a message to thewireless device indicating a resource for transmitting the BFR signal.

In an example, a gNB may transmit a response to a wireless device afterreceiving one or more BFR signals. The response may comprise the CRIassociated with the candidate beam the wireless device indicates in theone or multiple BFR signals.

Example of QCL

A base station may configure a wireless device with one or moreTCI-States by higher layer signaling. A number of the one or more TCIstates may depend on a capability of the wireless device. The wirelessdevice may use the one or more TCI-States to decode a PDSCH according toa detected PDCCH. Each of the one or more TCI-States state may includeone RS set TCI-RS-SetConfig. The one RS set TCI-RS-SetConfig may containone or more parameters. In an example, the one or more parameters may beused to configure quasi co-location relationship between one or morereference signals in the RS set and the DM-RS port group of the PDSCH.The one RS set may contain a reference to either one or two DL RSs andan associated quasi co-location type (QCL-Type) for each one configuredby the higher layer parameter QCL-Type. For the case of the two DL RSs,the QCL types may not be the same. In an example, the references of thetwo DL RSs may be to the same DL RS or different DL RSs. The quasico-location types indicated to the UE may be based on a higher layerparameter QCL-Type. The higher layer parameter QCL-Type may take one ora combination of the following types: QCL-TypeA′: {Doppler shift,Doppler spread, average delay, delay spread}; QCL-TypeB′: {Dopplershift, Doppler spread}; QCL-TypeC′: {average delay, Doppler shift} andQCL-TypeD′: {Spatial Rx parameter}.

In an example, a wireless device may receive an activation command. Theactivation command may be used to map one or more TCI states to one ormore codepoints of the DCI field Transmission Configuration Indication(TCI). After the wireless device receives a higher layer configurationof TCI states and before reception of the activation command, thewireless device may assume that one or more antenna ports of one DM-RSport group of PDSCH of a serving cell are spatially quasi co-locatedwith an SSB. In an example, the SSB may be determined in an initialaccess procedure with respect to Doppler shift, Doppler spread, averagedelay, delay spread, spatial Rx parameters, where applicable.

In an example, a wireless device may be configured, by a base station,with a higher layer parameter TCI-PresentInDCI. When the higher layerparameter TCI-PresentInDCI is set as ‘Enabled’ for a CORESET schedulinga PDSCH, the wireless device may assume that the TCI field is present ina DL DCI of a PDCCH transmitted on the CORESET. When the higher layerparameter TCI-PresentInDCI is set as ‘Disabled’ for a CORESET schedulinga PDSCH or the PDSCH is scheduled by a DCI format 1_0, for determiningPDSCH antenna port quasi co-location, the wireless device may assumethat the TCI state for the PDSCH is identical to the TCI state appliedfor the CORESET used for the PDCCH transmission.

When the higher layer parameter TCI-PresentinDCI is set as ‘Enabled’,the wireless device may use one or more TCI-States according to a valueof the ‘Transmission Configuration Indication’ field in the detectedPDCCH with DCI for determining PDSCH antenna port quasi co-location. Thewireless device may assume that the antenna ports of one DM-RS portgroup of PDSCH of a serving cell are quasi co-located with one or moreRS(s) in the RS set with respect to the QCL type parameter(s) given bythe indicated TCI state if the time offset between the reception of theDL DCI and the corresponding PDSCH is equal to or greater than athreshold Threshold-Sched-Offset. In an example, the threshold may bebased on UE capability. When the higher layer parameterTCI-PresentInDCI=‘Enabled’ and the higher layer parameterTCI-PresentInDCI=‘Disabled’, if the offset between the reception of theDL DCI and the corresponding PDSCH is less than the thresholdThreshold-Sched-Offset, the wireless device may assume that the antennaports of one DM-RS port group of PDSCH of a serving cell are quasico-located based on the TCI state used for PDCCH quasi co-locationindication of the lowest CORESET-ID in the latest slot in which one ormore CORESETs are configured for the UE. If all configured TCI states donot contain QCL-TypeD′, the wireless device may obtain the other QCLassumptions from the indicated TCI states for its scheduled PDSCHirrespective of the time offset between the reception of the DL DCI andthe corresponding PDSCH.

Example of a BFR Procedure.

In an NR system, when configured with multiple beams, a gNB and/or awireless device may perform one or more beam management procedure. Forexample, the wireless device may perform a BFR procedure, if one or morebeam pair links between the gNB and the wireless device fail.

FIG. 17 shows example of the BFR procedure. A wireless device mayreceive one or more RRC messages comprising BFR parameters. The one ormore RRC messages may comprise an RRC message (e.g. RRC connectionreconfiguration message, or RRC connection reestablishment message, orRRC connection setup message). The wireless device may detect at leastone beam failure according to at least one of BFR parameters. Thewireless device may start a first timer if configured in response todetecting the at least one beam failure. The wireless device may selecta selected beam in response to detecting the at least one beam failure.The selected beam may be a beam with good channel quality (e.g., RSRP,SINR, or BLER) from a set of candidate beams. The candidate beams may beidentified by a set of reference signals (e.g., SSBs, or CSI-RSs). Thewireless device may transmit at least a first BFR signal to a gNB inresponse to the selecting the selected beam. The at least first BFRsignal may be associated with the selected beam. The at least first BFRsignal may be a preamble transmitted on a PRACH resource, or a SR signaltransmitted on a PUCCH resource, or a beam indication transmitted on aPUCCH/PUSCH resource. The wireless device may transmit the at leastfirst BFR signal with a transmission beam corresponding to a receivingbeam associated with the selected beam. The wireless device may start aresponse window in response to transmitting the at least first BFRsignal. In an example, the response window may be a timer with a valueconfigured by the gNB. When the response window is running, the wirelessdevice may monitor a PDCCH in a first coreset. The first coreset may beassociated with the BFR procedure. In an example, the wireless devicemay monitor the PDCCH in the first coreset in condition of transmittingthe at least first BFR signal. The wireless device may receive a firstDCI via the PDCCH in the first coreset when the response window isrunning. The wireless device may consider the BFR procedure successfullycompleted when receiving the first DCI via the PDCCH in the firstcoreset before the response window expires. The wireless device may stopthe first timer if configured in response to the BFR proceduresuccessfully being completed. The wireless device may stop the responsewindow in response to the BFR procedure successfully being completed.

In an example, when the response window expires, and the wireless devicedoes not receive the DCI, the wireless device may increment atransmission number, wherein, the transmission number is initialized toa first number (e.g., 0) before the BFR procedure is triggered. If thetransmission number indicates a number less than the configured maximumtransmission number, the wireless device may repeat one or more actionscomprising at least one of: a BFR signal transmission; starting theresponse window; monitoring the PDCCH; incrementing the transmissionnumber if no response received during the response window is running. Ifthe transmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

Example BFR Procedure

A wireless device may receive one or more RRC messages comprising BFRparameters. The wireless device may detect at least one beam failureaccording to at least one of BFR parameters. The wireless device maystart a first timer if configured in response to detecting the at leastone beam failure. The wireless device may select a selected beam inresponse to detecting the at least one beam failure. The selected beammay be a beam with good channel quality (e.g., RSRP, SINR, or BLER) froma set of candidate beams. The candidate beams may be identified by a setof reference signals (e.g., SSBs, or CSI-RSs). The wireless device maytransmit at least a first BFR signal to a gNB in response to theselecting the selected beam. The at least first BFR signal may beassociated with the selected beam. The wireless device may transmit theat least first BFR signal with a transmission beam corresponding to areceiving beam associated with the selected beam. The at least BFRsignal may be a preamble transmitted on a PRACH resource, or a signal(e.g., SR, BFR request, and like) transmitted on a PUCCH resource, or abeam failure recovery signal transmitted on a PUCCH resource, or a beamreport transmitted on a PUCCH/PUSCH resource. The wireless device maystart a response window in response to transmitting the at least firstBFR signal. In an example, the response window may be a timer with avalue configured by the gNB. When the response window is running, thewireless device may monitor a PDCCH in a first coreset. The firstcoreset may be configured by the BFR parameters (e.g., RRC). The firstcoreset may be associated with the BFR procedure. In an example, thewireless device may monitor the PDCCH in the first coreset in conditionof transmitting the at least first BFR signal. The wireless device mayreceive a first DCI via the PDCCH in the first coreset when the responsewindow is running. The wireless device may consider the BFR proceduresuccessfully completed when receiving the first DCI via the PDCCH in thefirst coreset before the response window expires. The wireless devicemay stop the first timer if configured in response to the BFR proceduresuccessfully being completed. The wireless device may stop the responsewindow in response to the BFR procedure successfully being completed.

In an example, when the response window expires, and the wireless devicedoes not receive the DCI, the wireless device may, increment atransmission number, wherein, the transmission number is initialized toa first number (e.g., 0) before the BFR procedure is triggered. If thetransmission number indicates a number less than the configured maximumtransmission number, the wireless device may repeat one or more actionscomprising at least one of: a BFR signal transmission; starting theresponse window; monitoring the PDCCH; incrementing the transmissionnumber if no response received during the response window is running. Ifthe transmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured by an RRC with abeam failure recovery procedure. The beam failure recovery procedure maybe used for indicating to a serving base station of a new SSB or CSI-RSwhen a beam failure is detected. The beam failure may be detected on oneor more serving SSB(s)/CSI-RS(s) of the serving base station. In anexample, the beam failure may be detected by counting a beam failureinstance indication from a lower layer of the wireless device (e.g. PHYlayer) to the MAC entity.

In an example, an RRC may configure a wireless device with one or moreparameters in BeamFailureRecoveryConfig for a beam failure detection andrecovery procedure. The one or more parameters may comprisebeamFailureInstanceMaxCount for a beam failure detection;beamFailureDetectionTimer for the beam failure detection;beamFailureRecoveryTimer for the beam failure recovery procedure;rsrp-ThresholdSSB: an RSRP threshold for a beam failure recovery;powerRampingStep for the beam failure recovery;preambleReceivedTargetPower for the beam failure recovery;preambleTransMax for the beam failure recovery; and ra-ResponseWindow.The ra-ResponseWindow may be a time window to monitor one or moreresponses for the beam failure recovery using a contention-free RandomAccess preamble.

If a MAC entity of a wireless device transmits a contention-free randomaccess preamble for a beam failure recovery request (BFRQ), the MACentity may start ra-ResponseWindow at a first PDCCH occasion from theend of the transmitting the contention-free random access preamble. Thera-ResponseWindow may be configured in BeamFailureRecoveryConfig. Whilethe ra-ResponseWindow is running, the wireless device may monitor atleast one PDCCH (e.g. of an SpCell) for a response to the beam failurerecovery request. The beam failure recovery request may be identified bya C-RNTI.

In an example, if a MAC entity of a wireless device receives, from alower layer of the wireless device, a notification of a reception of atleast one PDCCH transmission and if the at least one PDCCH transmissionis addressed to a C-RNTI and if a contention-free random access preamblefor a beam failure recovery request is transmitted by the MAC entity,the wireless device may consider a random access procedure successfullycompleted.

In an example, a wireless device may initiate a contention-based randomaccess preamble for a beam failure recovery request. When the wirelessdevice transmits Msg3, a MAC entity of the wireless device may startra-ContentionResolutionTimer. The ra-ContentionResolutionTimer may beconfigured by RRC. In response to the starting thera-ContentionResolutionTimer, the wireless device may monitor at leastone PDCCH while the ra-ContentionResolutionTimer is running. In anexample, if the MAC entity receives, from a lower layer of the wirelessdevice, a notification of a reception of the at least one PDCCHtransmission; if a C-RNTI MAC-CE is included in the Msg3; if a randomaccess procedure is initiated for a beam failure recovery and the atleast one PDCCH transmission is addressed to a C-RNTI of the wirelessdevice, the wireless device may consider the random access proceduresuccessfully completed. In response to the random access procedure beingsuccessfully completed, the wireless device may stop thera-ContentionResolutionTimer.

In an example, if a random access procedure of a beam failure recoveryis successfully completed, the wireless device may consider the beamfailure recovery successfully completed.

A wireless device may be configured, for a serving cell, with a firstset of periodic CSI-RS resource configuration indexes by higher layerparameter Beam-Failure-Detection-RS-ResourceConfig. The wireless devicemay further be configured with a second set of CSI-RS resourceconfiguration indexes and/or SS/PBCH block indexes by higher layerparameter Candidate-Beam-RS-List. In an example, the first set and/orthe second set may be used for radio link quality measurements on theserving cell. If a wireless device is not provided with higher layerparameter Beam-Failure-Detection-RS-ResourceConfig, the wireless devicemay determine a first set to include SS/PBCH block indexes and periodicCSI-RS resource configuration indexes. In an example, the SS/PBCH blockindexes and the periodic CSI-RS resource configuration indexes may bewith same values as one or more RS indexes in one or more RS sets. In anexample, the one or more RS indexes in the one or more RS sets may beindicated by one or more TCI states. In an example, the one or more TCIstates may be used for respective control resource sets that thewireless device is configured for monitoring PDCCH. The wireless devicemay expect a single port RS in the first set.

In an example, a first threshold (e.g. Qout,LR) may correspond to afirst default value of higher layer parameterRLM-IS-OOS-thresholdConfig. In an example, a second threshold (e.g.Qin,LR) may correspond to a second default value of higher layerparameter Beam-failure-candidate-beam-threshold. A physical layer in thewireless device may assess a first radio link quality according to thefirst set of periodic CSI-RS resource configurations against the firstthreshold. For the first set, the wireless device may assess the firstradio link quality according to periodic CSI-RS resource configurationsor SS/PBCH blocks. In an example, the periodic CSI-RS resourceconfigurations or the SS/PBCH blocks may be associated (e.g. quasico-located) with at least one DM-RS of PDCCH monitored by the wirelessdevice.

In an example, the wireless device may apply the second threshold to afirst L1-RSRP for SS/PBCH blocks. The wireless device may apply thesecond threshold to a second L1-RSRP for periodic CSI-RS resources afterscaling a respective CSI-RS reception power with a value provided byhigher layer parameter Pc_SS.

In an example, a physical layer in a wireless device may, in slots wherethe first radio link quality according to the first set is assessed,provide an indication to higher layers (e.g. MAC). The wireless devicemay provide an indication to higher layers when the first radio linkquality for all corresponding resource configurations in the first setis worse than the first threshold. The wireless device may use the allcorresponding resource configurations in the first set to assess thefirst radio link quality. The physical layer may inform the higherlayers (e.g. MAC, RRC) when the first radio link quality is worse thanthe first threshold with a first periodicity. The first periodicity maybe determined by a maximum between the shortest periodicity of periodicCSI-RS configurations or SS/PBCH blocks in the first set and X (e.g. 2ms).

In an example, in response to a request from higher layers (e.g. MAC), awireless device may provide to the higher layers the periodic CSI-RSconfiguration indexes and/or SS/PBCH block indexes from the second set.The wireless device may further provide, to the higher layers,corresponding L1-RSRP measurements that are larger than or equal to thesecond threshold.

A wireless device may be configured with one control resource set(coreset) by higher layer parameterBeam-failure-Recovery-Response-CORESET. The wireless device may befurther configured with an associated search space provided by higherlayer parameter search-space-config. The associated search space may beused for monitoring PDCCH in the one control resource set. The wirelessdevice may receive from higher layers (e.g. MAC), by parameterBeam-failure-recovery-request-RACH-Resource, a configuration for a PRACHtransmission. For the PRACH transmission in slot n and according toantenna port quasi co-location parameters associated with periodicCSI-RS configuration or SS/PBCH block with a first RS index, thewireless device may monitor the PDCCH for detection of a DCI formatstarting from slot n+4 within a window. The window may be configured byhigher layer parameter Beam-failure-recovery-request-window. The DCIformat may be with CRC scrambled by C-RNTI. For a PDSCH reception, thewireless device may assume the antenna port quasi-collocation parameters(e.g. as for monitoring the PDCCH) until the wireless device receives byhigher layers an activation for a TCI state or a parameterTCI-StatesPDCCH.

Example SR

In an example, a wireless device may trigger a SR for requesting UL-SCHresource when the wireless device has new transmission. A gNB maytransmit to a wireless device at least one message comprising parametersindicating zero, one or more SR configurations. A SR configuration maycomprise a set of PUCCH resources for SR on one or more BWPs, and/or oneor more cells. On a BWP, at most one PUCCH resource for SR may beconfigured. Each SR configuration may correspond to one or more logicalchannels. Each logical channel may be mapped to zero or one SRconfiguration configured by the at least one message. A SR configurationof a logical channel (LCH) that triggers a buffer status report (BSR)may be considered as a corresponding SR configuration for a triggeredSR.

In an example, for each SR configuration, the at least one message mayfurther comprise one or more parameters indicating at least one of: a SRprohibit timer; a maximum number of SR transmission; a parameterindicating a periodicity and offset of SR transmission; and/or a PUCCHresource. In an example, the SR prohibit timer may be a duration duringwhich the wireless device may be not allowed to transmit the SR. In anexample, the maximum number of SR transmission may be a transmissionnumber for which the wireless device may be allowed to transmit the SRat most.

In an example, a PUCCH resource may be identified by at least: frequencylocation (e.g., starting PRB); a PUCCH format associated with initialcyclic shift of a base sequence and time domain location (e.g., startingsymbol index). In an example, a PUCCH format may be PUCCH format 0, orPUCCH format 1, or PUCCH format 2, or PUCCH format 3, or PUCCH format 4.A PUCCH format 0 may has a length of 1 or 2 OFDM symbols and is lessthan or equal to 2 bits. A PUCCH format 1 may occupy a number between 4and 14 of OFDM symbols and is less than or equal to 2 bits. A PUCCHformat 2 may occupy 1 or 2 OFDM symbols and is greater than 2 bits. APUCCH format 3 may occupy a number between 4 and 14 of OFDM symbols andis greater than 2 bits. A PUCCH format 4 may occupy a number between 4and 14 of OFDM symbols and is greater than 2 bits.

In an example, a PUCCH format for SR transmission may be a PUCCH format0, or PUCCH format 1. A wireless device may transmit a PUCCH in a PUCCHresource for a corresponding SR configuration only when the wirelessdevice transmits a positive SR. For a positive SR transmission usingPUCCH format 0, a wireless device may transmit a PUCCH by setting thecyclic shift to a first value (e.g., 0). For a positive SR transmissionusing PUCCH format 1, a wireless device may transmit a PUCCH by settinga first bit, before BPSK modulated on a sequence, to a first value(e.g., 0).

In an example, a SR may be multiplexed with HARQ-ACK or CSI on a PUCCHformat. When a positive SR multiplexed with HARQ-ACK, a wireless devicemay decide a cyclic shift of the base sequence based on the initialcyclic shift and a first cyclic shift based on one or more values of oneor more HARQ-ACK bits. When a negative SR multiplexed with HARQ-ACK, awireless device may decide a cyclic shift of the base sequence based onthe initial cyclic shift and a second cyclic shift based on one or morevalue of the one or more HARQ-ACK bits. The first cyclic shift isdifferent from the second cyclic shift.

In an example, a wireless device may maintain a SR transmission counter(e.g., SR_COUNTER) associated with a SR configuration.

In an example, if an SR of a SR configuration is triggered, and thereare no other SRs pending corresponding to the same SR configuration, awireless device may set the SR_COUNTER of the SR configuration to afirst value (e.g., 0).

In an example, when an SR is triggered, a wireless device may considerthe SR pending until it is cancelled. In an example, when one or more ULgrants accommodate all pending data available for transmission, allpending SR(s) may be cancelled.

In an example, a wireless device may determine one or more PUCCHresources on an active BWP as valid PUCCH resources at a time of SRtransmission occasion.

In an example, a wireless device may transmit a PUCCH in a PUCCHresource associated with a SR configuration when the wireless devicetransmits a positive SR. In an example, a wireless device may transmitthe PUCCH using PUCCH format 0, or PUCCH format 1, according to thePUCCH configuration.

In an example, a wireless device may receive one or more RRC messagecomprising parameters of one or more SR configurations. In an example,for each of the one or more SR configurations, the parameters mayindicate at least one of: a SR prohibit timer; a maximum number of SRtransmission; a parameter indicating a periodicity and offset of SRtransmission; and/or a PUCCH resource identified by a PUCCH resourceindex. In an example, when a SR of a SR configuration triggered(therefore in pending now) in response to a BSR being triggered on a LCHcorresponding to the SR configuration, a wireless device may set aSR_COUNTER to a first value (e.g., 0), if there is no other pending SRscorresponding to the SR configuration.

In an example, a wireless device may determine whether there is at leastone valid PUCCH resource for the pending SR at the time of SRtransmission occasion. If there is no valid PUCCH resource for thepending SR, the wireless device may initiate a random access procedureon a PCell. The wireless device may cancel the pending SR in response tono valid PUCCH resource for the pending SR.

In an example, if there is at least one valid PUCCH resource for thepending SR, a wireless device may determine an SR transmission occasionon the at least one valid PUCCH resource based on the periodicity andthe offset of SR transmission. In an example, if the SR prohibit timeris running, the wireless device may wait for another SR transmissionoccasion. In an example, if the SR prohibit timer is not running; and ifthe at least one valid PUCCH resource for the SR transmission occasiondoes not overlap with a measurement gap; and if the at least one validPUCCH resource for the SR transmission occasion does not overlap with anuplink shared channel (UL-SCH) resource; if the SR_COUNTER is less thanthe maximum number of SR transmission, the wireless device may incrementthe SR_COUNTER (e.g., by one), instruct the physical layer of thewireless device to signal the SR on the at least one valid PUCCHresource for the SR. The physical layer of the wireless device maytransmit a PUCCH on the at least one valid PUCCH resource for the SR.The wireless device may monitor a PDCCH for detecting a DCI for uplinkgrant in response to transmitting the PUCCH.

In an example, if a wireless device receives one or more uplink grantswhich may accommodate all pending data available for transmission, thewireless device may cancel the pending SR, and/or stop the SR prohibittimer.

In an example, if the wireless device does not receive one or moreuplink grants which may accommodate all pending data available fortransmission, the wireless device may repeat one or more actionscomprising: determining the at least one valid PUCCH resource; checkingwhether the SR prohibit timer is running; whether the SR_COUNTER isequal or greater than the maximum number of SR transmission;incrementing the SR_COUNTER, transmitting the SR and starting the SRprohibit timer; monitoring a PDCCH for uplink grant.

In an example, if the SR_COUNTER indicates a number equal to or greaterthan the maximum number of SR transmission, a wireless device mayrelease PUCCH for one or more serving cells, and/or release SRS for theone or more serving cells, and/or clear one or more configured downlinkassignments and uplink grants, and/or initiate a random access procedureon a PCell, and/or cancel all the pending SRs.

Example of Scheduling Request-Based Procedure for BFR Procedure.

In an example, a gNB and a wireless device may perform a PRACH-based BFRprocedure when at least one beam failure instance is identified if abeam correspondence exists between the gNB and the wireless device. Inan example, a beam correspondence may exist when a wireless devicetransmits an uplink signal using a transmission beam corresponding to areceiving beam for receiving a downlink signal from the gNB. When thewireless device identifies the receiving beam, for example, bydetermining an RF and/or digital beamforming parameters for receivingthe downlink signal from the gNB, the wireless device may determine thetransmission beam by using an RF and/or digital beamforming parameterscorresponding to beamforming parameters for the receiving beam. Forexample, the beamforming parameters (e.g., beam weight factors onantenna elements) for the transmission beam may be same as that for thereceiving beam in case of beam correspondence existence. The beamcorrespondence existence may simplify transceiver design in some case,since a wireless device may determine a transmission beam based on areceiving beam. In an example, with beam correspondence, a gNB may notnecessarily indicate the transmission beam used for a downlink or anuplink transmission, therefore reducing the signaling overhead. In anexample, with beam correspondence, a wireless device may avoid uplinkbeam sweeping to help a gNB find a proper uplink beam, thereforereducing the power consumption of the wireless device. In an example,the proper beam may be in the direction of the wireless device. Beamcorrespondence may exist in some scenario, for example, in a TDD case,or when transmission and reception share the same set of physicalantenna elements, and/or when transmission and reception have a same orsimilar beam width.

In an example, a beam correspondence may not exist, when physicalantenna for transmission is separated from physical antenna forreception, and/or the beam widths for transmission and reception aredifferent. In an example, a wireless device may not determine atransmission beam based on a receiving beam. The receiving beam may beused for receiving downlink signals. In such case, a gNB may indicateexplicitly a transmission beam of PUCCH/PUSCH transmission, for example,by a RRC message, or a MAC CE, or a DCI. In an example, a gNB and awireless device may not perform a PRACH-based BFR procedure when atleast one beam failure instance is identified if a beam correspondencedoes not exist.

When beam correspondence does not exist, in existing PRACH-based BFRprocedure, a wireless device may determine, for PRACH preambletransmission, a transmission beam associated with the receiving beam forreceiving a candidate beam. However, the gNB may not detect the PRACHpreamble since the gNB may not expect that there is an uplinktransmission on the transmission beam on which the wireless devicetransmits the PRACH preamble, due to no beam correspondence between thetransmission beam and the receiving beam in the gNB and/or the wirelessdevice. In this case, the PRACH-based BFR procedure may result in anunsuccessful beam failure recovery. The unsuccessful beam failurerecovery may further lead to a radio link failure.

In an example, when a beam correspondence does not exist, a wirelessdevice may transmit a PUCCH signal to a gNB indicating a BFR procedureis triggered, when at least one beam failure instance is identified. Atransmission beam for the PUCCH signal may be indicated by a RRCmessage, or a MAC CE, or a DCI. However, HARQ is not supported inexisting PUCCH transmission. For example, a wireless device may transmita CSI report to a gNB on a PUCCH resource. The gNB may not transmit aresponse to the wireless device for a confirmation of receiving the CSIreport, even if the gNB receives the CSI report. For example, a wirelessdevice may transmit a HARQ-ACK feedback to a gNB on a PUCCH resource.The gNB may not transmit a response to the wireless device to confirm areception of receiving the HARQ-ACK feedback. For a BFR procedure, aftera wireless device transmits a PUCCH signal to a gNB, the wireless devicemay expect to receive a response from the gNB. When no response isreceived from the gNB, the wireless device may determine to repeattransmitting the PUCCH signal. Therefore, a mechanism for a gNB'sconfirmation in response to a PUCCH signal transmission is necessary.The gNB's confirmation may ensure that the wireless device and the gNBinteract properly to complete the BFR procedure. Example embodimentsprovide methods to enhance an SR based, or an SR-like BFR procedure whenbeam correspondence does not exist.

In existing SR configurations, an SR configuration may correspond to atleast one logical channel. An SR configuration may be associated withmultiple parameters comprising at least one of: an SR prohibit timer; amaximum number of SR transmissions; a parameter indicating a periodicityand offset of the SR transmissions; and/or a PUCCH resource.

In an example, when an SR-like procedure is used for a BFR procedure, anSR-like configuration for the BFR procedure may be different from an SRconfiguration associated with at least one logical channel. For example,a wireless device may transmit a pending SR at most 64 times for the SRconfiguration associated with the at least one logical channel. In anexample, a wireless device may transmit an SR at most 200 times for theSR-like configuration for the BFR procedure, for example, consideringthe beam correspondence may not exist. In an example, a response windowfor the BFR procedure may be shorter than that for an SR for requestingan UL-SCH resource. For example, a response timer associated with theBFR procedure may be at most 80 slots subject to a first configuration.An SR prohibit timer for the SR configuration for the requesting theUL-SCH resource may be at most 128 ms subject to a second configuration.Therefore, an SR-like configuration for a BFR procedure may beseparately or independently configured from an SR configuration forrequesting an UL-SCH resource.

In an example, when an SR-like procedure (e.g., PUCCH based) is used fora BFR procedure, the SR-like procedure triggered by the BFR proceduremay be different from an SR procedure triggered by requesting UL-SCHresource (e.g., BSR triggered).

FIG. 18 shows an example of PUCCH-based BFR procedure. A gNB maytransmit at least one message comprising parameters indicating a firstset of RSs (e.g., RS 0) and a second set of RSs (e.g., RS 1, RS 2 and RS3). The at least one message may be a RRC message (e.g. RRC connectionreconfiguration message, or RRC connection reestablishment message, orRRC connection setup message). The first set of RSs may identify one ormore beams QCLed with a beam on which the gNB transmits PDCCH/PDSCHs.The second set of RSs may identify one or more candidate beams fromwhich the wireless device may select a candidate beam with qualitybetter than a first threshold when the one or more beams associated withthe first set of RSs fail. In an example, each of the first/second setof RSs may be a SSB, or a CSI-RS. The first threshold may be aconfigured value based on BLER, or SINR, or L1-RSRP. In an example, theone or more beams associated with the first set of RSs fail whenmeasurement on the first set of RSs are worse than a configured secondthreshold (e.g., RSRP, or BLER).

In an example, the at least one message may comprise configurationparameters. In an example, the configuration parameters may indicate afirst request (e.g., scheduling request, or a beam failure request, or abeam request) configuration, and at least a second sr (e.g., schedulingrequest) configuration. The first request configuration may beassociated with at least one of: a first PUCCH resource; a first timerwith a first value; a first transmission number; a first periodicity fora transmission of the first request; and/or a first offset for thetransmission of the first request. In an example, the at least second srconfiguration may be associated with at least one of: a second PUCCHresource; a second timer with a second value; a second transmissionnumber; a second periodicity; and/or a second offset. In an example, theat least second SR configuration may be associated with at least onelogical channel.

In an example, the first value for the first timer may be different fromthe second value of the second timer. In an example, the firsttransmission number may be different from the second transmissionnumber. In an example, the first periodicity may be different from thesecond periodicity. In an example, the first offset may be differentfrom the second offset. In an example, the first PUCCH resource may bedifferent from the second PUCCH resource.

In an example, the wireless device may maintain a first counter for thefirst request configuration. In an example, the wireless device maymaintain a second counter for each of the at least second srconfiguration.

In an example, the at least one message may comprise parametersindicating a first control resource set, and at least a second controlresource set. The first control resource set may be associated with thefirst request configuration. In an example, when a wireless devicetransmits a first request on the first PUCCH resource for a BFRprocedure, the wireless device may monitor a first PDCCH on the firstcontrol resource set. In an example, when a wireless device transmits asecond sr of the at least second sr configuration, the wireless devicemay monitor a second PDCCH on the at least second control resource set.

In an example, when a random-access procedure is initiated for a beamfailure recovery of a downlink BWP, a BWP inactivity timer associatedwith the downlink BWP may be stopped. In an example, in response to thestopping the BWP inactivity timer, the wireless device may not switchthe downlink BWP due to an expiry of the BWP inactivity timer. In anexample, the stopping the BWP inactivity timer may avoid a misalignment,between a base station and a wireless device, on the downlink BWP thewireless device is operating on. In an example, the base station maytransmit a BFR response (e.g., random-access response, beam failurerecovery response) on the downlink BWP to complete the random-accessprocedure. The wireless device may complete the random-access procedurefor the beam failure recovery in response to the receiving the BFRresponse on the downlink BWP. In an example, the wireless device mayavoid missing the receiving the BFR response from the base station inresponse to the stopping the BWP inactivity timer.

In an example, in existing procedures, a BWP inactivity timer of adownlink BWP may not be stopped when an uplink transmission via a PUCCHresource is initiated. If the existing procedures for the uplinktransmission via the PUCCH resource are used for a PUCCH-based BFRprocedure, the wireless device may not stop a BWP inactivity timer of adownlink BWP in response to the initiating an uplink transmission via aPUCCH resource for the PUCCH based BFR procedure of the downlink BWP. Inan example, the BWP inactivity timer may expire during the PUCCH basedBFR. In response to the expiry of the BWP inactivity timer, the wirelessdevice may switch the downlink BWP to a default downlink BWP. In anexample, the base station may not be aware of the switching. The basestation may transmit a BFR response on the downlink BWP to complete thePUCCH-based BFR. In an example, the wireless device may not receive theBFR response due to the switching the downlink BWP. This may result indelay, signaling overhead, interference in PUCCH-based BFR procedures.

Example embodiments enhance PUCCH-based BFR to improve downlink radioefficiency, reduce uplink signaling overhead and reduce a duration.

FIG. 19 shows an example embodiment. In an example, a wireless devicemay receive one or more messages comprising configuration parameters intime T0. The one or more messages may comprise one or more RRC messages.In an example, the configuration parameters may comprise bandwidth part(BWP) configuration parameters for a plurality of BWPs comprising afirst BWP (e.g. default BWP) and a second BWP (non-default BWP). Theconfiguration parameters may further comprise one or more beam failurerecovery (BFR) configuration parameters. The one or more BFRconfiguration parameters may comprise a first set of RS resourceconfigurations for the second BWP. The first set of RS resourceconfigurations may comprise one or more first RSs (e.g., CSI-RS or SSblocks) of the second BWP. The one or more BFR configuration parametersmay further comprise a second set of RS resource configurationscomprising one or more second RSs (e.g., CSI-RS or SS blocks) of thesecond BWP. The wireless device may measure radio link quality of one ormore beams associated with the one or more first RSs and/or the one ormore second RSs.

In an example, the one or more BFR configuration parameters may furthercomprise one or more beam failure recovery request (BFRQ) resourcesassociated with the second BWP. In an example, the one or more BFRconfiguration parameters may further comprise an association betweeneach of the one or more second RSs and each of the one or more BFRQresources.

In an example, a wireless device may receive a first DCI indicatingswitching a current active BWP to the second BWP. In an example, thefirst DCI may comprise a BWP indicator. The wireless device maydetermine that the first DCI indicates BWP switching in response to theBWP indicator indicating a BWP different from the current active BWP. Inan example, the wireless device may start an inactivity timer of thesecond BWP in response to switching the current active BWP to the secondBWP.

In an example, the wireless device may assess a first radio link qualityof the one or more first RSs against a first threshold. In an example,the first threshold (e.g. hypothetical BLER, L1-RSRP) may be a firstvalue provided by a higher layer (e.g. RRC, MAC). The wireless devicemay monitor at least one PDCCH of the second BWP. At least one RS (e.g.,DM-RS) of the at least one PDCCH may be associated (e.g., QCLed) withthe one or more first RSs.

A wireless device may detect a beam failure on the second BWP when thefirst radio link quality of the one or more first RSs meets certaincriteria (time T1). For example, a beam failure may occur when RSRP/SINRof the one or more first RSs is lower than the first threshold and/orBLER is higher than the first threshold. The assessment may be for aconsecutive number of times with a value provided by a higher layer(e.g. RRC, MAC).

In response to detecting the beam failure on the second BWP, thewireless device may initiate a PUCCH-based beam failure recovery (BFR)procedure for the second BWP (time T2). In an example, T1 and T2 may besame. In an example, T1 and T2 may be different. In response toinitiating the PUCCH based BFR procedure, the wireless device may stopthe inactivity timer of the second BWP. In an example, the stopping theinactivity timer may avoid switching the second BWP during the PUCCHbased BFR procedure. In an example, the stopping the inactivity timermay enable the wireless device not to miss a BFR response of the basestation to complete the PUCCH-based BFR procedure.

In an example, in response to initiating the PUCCH based BFR procedurethe wireless device may start a BFR timer (if configured) and/orinitiate a candidate beam identification procedure. In an example, theBFR timer may be similar to beamFailureRecoveryTimer. The BFR timer maybe used in PUCCH-based BFR procedure. For the candidate beamidentification procedure, the wireless device may identify a first RS inthe one or more second RSs. The first RS may be associated with a BFRQresource of the one or more BFRQ resources. The BFRQ resource maycomprise at least one PUCCH (e.g. time and/or frequency) resource. In anexample, a second radio link quality (e.g. BLER, L1-RSRP) of the firstRS may be better (e.g. lower BLER or higher L1-RSRP or higher SINR) thana second threshold. In the example, the second threshold may be a secondvalue provided by the higher layer (e.g. RRC, MAC).

In an example, in response to detecting the beam failure on the secondBWP and identifying the first RS of the second BWP, the wireless devicemay initiate a beam failure recovery request (BFRQ) transmission. TheBFRQ transmission may comprise transmitting, in a first slot, at leastone PUCCH signal via the at least one PUCCH resource for the PUCCH-basedBFR procedure of the second BWP (time T3). In an example, the at leastone PUCCH signal may be a bit. In an example, the bit may be set to afirst value (e.g., one), indicating: the PUCCH-based BFR procedure istriggered; and/or a candidate beam (e.g., the first RS) associated withthe at least one PUCCH resource is identified.

In response to transmitting the at least one PUCCH signal in the firstslot, the wireless device may start, from a second slot, monitoring fora BFR response. The monitoring for the BFR response may comprisemonitoring at least one second PDCCH in one or more coresets associatedwith the second BWP for a second DCI (e.g. a downlink assignment or anuplink grant) within a configured response window (or when a first timerwith a first value is running). The second DCI may be with CRC scrambledby a C-RNTI of the wireless device. In an example, the one or morecoresets may be dedicated for a beam failure recovery. In an example,the one or more coresets may be configured with the one or more BFRconfiguration parameters.

In an example, in response to receiving the second DCI on the at leastone second PDCCH in the one or more coresets, within the configuredresponse window, the PUCCH-based BFR procedure may be successfullycompleted (time T4). In an example, in response to the PUCCH-based BFRprocedure being successfully completed, the wireless device may restartthe inactivity timer of the second BWP (time T4).

In an example, when the BFR timer expires before the completion of thePUCCH-based BFR procedure, the wireless device may complete thePUCCH-based BFR procedure unsuccessfully.

In an example, in response to the completing the PUCCH based BFRprocedure unsuccessfully, the wireless device may initiate arandom-access procedure (e.g., contention based random-access) for abeam failure recovery of the second BWP.

In an example, the at least one PUCCH resource may overlap with ameasurement gap. In an example, the wireless device may transmit the atleast one PUCCH signal via the at least one PUCCH resource for thePUCCH-based BFR procedure regardless of the measurement gap.

In an example, when the wireless device initiates the PUCCH-based BFRprocedure, the wireless device may set a first counter to a first value(e.g., 0). In an example, if the first counter indicates a value lessthan the first transmission number, the wireless device may transmit theat least one PUCCH signal via the at least one PUCCH resource for thePUCCH-based BFR procedure.

In an example, a wireless device may increment the first counter (e.g.,by one), and/or start the first timer with the first value, in responseto transmitting the at least one PUCCH signal via the at least one PUCCHresource.

In an example, if the first counter indicates a value greater (orgreater than or equal) the first transmission number, the wirelessdevice may complete the PUCCH-based BFR procedure unsuccessfully.

In an example, in response to the completing the PUCCH based BFRprocedure unsuccessfully, the wireless device may initiate arandom-access procedure (e.g., contention based random-access) for abeam failure recovery of the second BWP

FIG. 20 shows an example embodiment. The procedures performed at time T0and T1 of FIG. 20 are similar to the ones of FIG. 19 performed at timeT0 and T1.

In an example, in response to detecting the beam failure on the secondBWP, the wireless device may initiate a PUCCH-based beam failurerecovery (BFR) procedure for the second BWP (time T1). In response tothe initiating the PUCCH based BFR procedure, the wireless device maynot stop the inactivity timer of the second BWP. In an example, inresponse to the initiating the PUCCH based BFR procedure, the wirelessdevice may start, if configured, a BFR timer (BFR timer in FIG. 20 ). Inan example, in response to initiating the PUCCH based BFR procedure thewireless device may set a first counter (BFR counter in FIG. 20 ) to afirst value (e.g., 0).

In an example, a wireless device may increment the first counter (e.g.,by one), and/or start a first timer (e.g., Response window in FIG. 20 )with a first value, in response to transmitting the at least one PUCCHsignal via the at least one PUCCH resource.

In an example, the PUCCH-based BFR procedure may be completedunsuccessfully in response to the BFR timer (if configured) expiring. Inan example, the PUCCH-based BFR procedure may be completedunsuccessfully in response to the first counter indicating a valuegreater than or equal to the first transmission number.

In an example, the inactivity timer of the second BWP may expire duringthe PUCCH-based BFR procedure (time T4).

In an example, the inactivity timer of the second BWP may expire beforethe PUCCH-based BFR procedure is completed (e.g., successfully orunsuccessfully). In an example, the inactivity timer of the second BWPmay expire when the first counter indicating a value less than the firsttransmission number (e.g., N in FIG. 20 is less than the firsttransmission number).

In an example, in response to the inactivity timer expiring, thewireless device may abort the PUCCH-based BFR procedure. In an example,in response to the aborting the PUCCH-based BFR procedure, the wirelessdevice may at least: reset the BFR timer (e.g., BFR timer in FIG. 20 ),reset the first counter (BFR counter in FIG. 20 ), or reset the firsttimer (e.g., Response window in FIG. 20 ).

In an example, the wireless device may switch to a default downlink BWPin response to the inactivity timer expiring.

In an example, the resetting the BFR timer, the first counter or thefirst timer may avoid continuing the PUCCH-based BFR in the defaultdownlink BWP. The default DL BWP may be configured with a different setof RS resource configurations for PDCCH monitoring. In an example, thedifferent set of RS resource configurations may have a good (e.g., lowerBLER than the first threshold, higher SINR than the first threshold, orhigher L1-RSRP than the first threshold) radio link quality.

In an example, a wireless device may receive from a base station, one ormore messages. The one or more messages may comprise one or moreconfiguration parameters of a cell. In an example, the one or moreconfiguration parameters may indicate at least: a beam failure instancecounter of a BWP of the cell and one or more physical uplink controlchannel (PUCCH) resources of the BWP for a beam failure recoveryprocedure.

In an example, the one or more configuration parameters may furtherindicate a value of a BWP inactivity timer. In an example, the BWPinactivity timer may be configured for the cell. In an example, the BWPinactivity timer may be configured for the BWP. In an example, thewireless device may start the BWP inactivity timer associated with theBWP in response to switching to the BWP as an active BWP.

In an example, the switching may be performed in response to receiving afirst downlink control information (DCI) comprising a BWP indicator. Thewireless device may determine that the first DCI indicates BWP switchingin response to the BWP indicator indicating the BWP (e.g., differentfrom current active BWP). In an example, the switching may be performedin response to receiving an RRC signal indicating BWP switching.

In an example, the switching to the BWP as the active BWP may comprisemonitoring a downlink control channel of the BWP.

In an example, the one or more configuration parameters may furtherindicate at least: one or more first reference signals (RSs) of the BWP,one or more second RSs of the BWP, and radio resources of a dedicatedcontrol resource set (coreset) on the BWP. In an example, the one ormore first RSs may comprise one or more first CSI-RSs and/or one or morefirst synchronization signal (SS) blocks. In an example, the one or moresecond RSs may comprise one or more second CSI-RSs and/or one or moresecond SS blocks.

In an example, the one or more configuration parameters may furtherindicate an association between each of the one or more second RSs andeach of the one or more PUCCH resources.

In an example, the wireless device may determine a number of beamfailure instance indications associated with the BWP reaching to thebeam failure instance counter. In an example, the beam failure instanceindication may comprise assessing the one or more first RSs of the BWPwith radio quality lower than a first threshold. The first threshold maybe based on hypothetical BLER, or RSRP, or RSRQ, or SINR. The firstthreshold may be configured by RRC signaling.

In an example, in response to determining a number of beam failureinstance indications associated with the BWP reaching to the beamfailure instance counter, the wireless device may initiate the beamfailure recovery procedure. In an example, the beam failure recoveryprocedure may comprise selecting a selected RS, in the one or moresecond RSs. The selected RS may be associated with a PUCCH resource. ThePUCCH resource may be one of the one or more PUCCH resources. The PUCCHresource may comprise at least one channel resource. In an example, theat least one channel resource may comprise one or more time resourcesand/or one or more frequency resources.

In an example, the beam failure recovery procedure may further comprisetransmitting, a signal via the at least one channel resource andmonitoring, for a second DCI, the dedicated coreset.

In an example, the selected RS may be associated with one of the one ormore second RSs with radio quality higher than a second threshold. Thesecond threshold may be based on L1-RSRP, or RSRQ, or hypothetical BLER,or SINR. The second threshold may be configured by RRC signaling.

In an example, the wireless device may stop the BWP inactivity timer inresponse to the initiating the beam failure recovery procedure. Thewireless device may transmit the signal via the PUCCH resource of theone or more PUCCH resources.

In an example, the monitoring the dedicated coreset may comprisesearching for the second DCI in the dedicated coreset addressed for anidentifier (e.g., C-RNTI) associated with the wireless device. In anexample, the wireless device may receive the second DCI on the dedicatedcoreset. In an example, the wireless device may restart the BWPinactivity timer in response to receiving the second DCI on thededicated coreset.

In an example, a wireless device may be configured with one or more SRconfigurations. In an example, each of the one or more SR configurationscomprising SR-config1 and SR-config2 may have different (e.g.,non-overlapping, fully-overlapping, partially overlapping) PUCCHresources with different or same periodicity.

In an example, the wireless device may transmit one SR at a given time(or in a TTI). In an example, a first PUCCH resources associatedSR-config1 may overlap with a second PUCCH resources associated withSR-config2 in time (e.g., in same TTI). In an example, when a firstpending SR of SR-config1 and a second pending SR of SR-config2 aretriggered (e.g., in a same TTI, slot, frame), the wireless device mayselect an SR configuration triggered by logical channel with a higherpriority. In an example, if SR-config1 and SR-config2 are configured foreMBB and URLLC services, respectively, the wireless device may selectSR-config2, which has a higher priority (or triggered by a logicalchannel with a higher priority). The wireless device may transmit thesecond pending SR via the second PUCCH resources. In an example, thewireless device may delay the transmission of the first pending SR untilthe first PUCCH resources for the first pending SR do not overlap withthe second PUCCH resources for the second pending SR.

When a similar procedure is implemented for a PUCCH-based BFR procedure,a wireless device may delay a transmission of a triggered request (e.g.,may be called scheduling request, or a beam failure request, or a beamrequest, or a beam failure recovery request, PUCCH-based BFR, and/or thelike etc.) for a BFR procedure until at least one valid PUCCH resourcefor the triggered request does not overlap with a PUCCH resource fortransmission of a pending SR. When existing procedures are implemented,a BFR timer configured by RRC may expire and the PUCCH-based BFRprocedure may complete unsuccessfully. Implementation of existingprocedures may result be inefficient and may result in an increase inradio link failure (RLF).

In an example, when existing procedures are implemented, at least onevalid PUCCH resource for a transmission occasion of a triggered requestfor a BFR procedure may overlap with a PUCCH resource for transmissionof a pending SR. If the wireless device drops (or delays) the triggeredrequest and transmits an uplink signal (e.g. SR) on the PUCCH resource,a base station may transmit one or more acknowledgement (ACK) signalsassociated with the uplink signal. In an example, the wireless devicemay monitor at least one PDCCH in one or more coresets for the one ormore ACK signals. In an example, during the BFR procedure, the at leastone PDCCH may fail (e.g., radio link quality lower than a threshold). Inan example, the wireless device may not receive the one or more ACKsignals. In response to the not receiving the one or more ACK signals,the wireless device may retransmit the uplink signal. Implementation ofexisting procedures may result in signaling overhead, transmissionlatency and waste of resources. In an example, transmitting an uplinksignal via the PUCCH resource during a BFR procedure may increase thetransmission latency.

In an example embodiment, a wireless device may initiate a BFR procedurebased on detecting a beam failure. A first PUCCH resource configured forthe BFR procedure of the wireless device may overlap in time (e.g., atleast one symbol, at least one mini-slot, at least one slot, etc.) witha second PUCCH resource configured for a scheduling request (e.g., forUL-SCH transmission, data transmission, to request an uplink grant) ofthe wireless device. The wireless device may not transmit a firstrequest (e.g., BFRQ), for the BFR procedure, via the first PUCCHresource and a second request (e.g., SR), for the scheduling request,via the second PUCCH resource simultaneously. The wireless device maynot be capable of at least two simultaneous PUCCH transmissions (e.g.,power limited, RF-capability limited, etc.). The wireless device maydrop the transmission of the first request for the BFR procedure andtransmit the second request for the scheduling request. Dropping thetransmission of the first request for the BFR procedure may createinefficiencies. In an example, the wireless device may not receive anuplink grant, from a base station receiving the second request, for thescheduling request based on the beam failure at the wireless device. Thewireless device may detect the beam failure based on the quality ofdownlink control channels of the wireless device being worse (e.g.,higher BLER, lower SINR, lower RSRP, etc.) than a threshold. Thewireless device may not receive the uplink grant via the downlinkcontrol channels with the beam failure. This may result inretransmission of the second request leading to increased interferenceto other cells and wireless device. This may result in delayed datatransmission (e.g., UL-SCH). This may delay the completion of the BFRprocedure. There is a need to implement an enhanced procedure for theBFR of the wireless device.

Example embodiments implement an enhanced BFR procedure when a firstrequest for a BFR procedure overlaps, in time, with a second request fora scheduling request. A wireless device may drop the transmission of thesecond request and transmit the first request. The wireless device maycomplete the BFR procedure earlier based on the dropping thetransmission of the second request and transmitting the first request.This enhanced process improves uplink control signaling, reduces uplinkoverhead (e.g., reduce retransmissions) and interference, and reduceswireless device battery power consumption (e.g. by reducing monitoring,for an uplink grant, downlink control channels with a beam failure). Thewireless device may reestablish connection with the base station beforedeclaring radio-link-failure (RLF).

Example embodiments enhance PUCCH-based BFR procedures to improvedownlink radio efficiency and reduce uplink signaling overhead andreduce a duration of a BFR procedure.

FIG. 21 shows an example embodiment. The procedures at time T0, T1 andT2 of FIG. 19 are similar in this embodiment. In response to detecting abeam failure, a wireless device may initiate a PUCCH-based beam failurerecovery (BFR) procedure. In an example, the wireless device may triggera first request for the PUCCH-based BFR procedure.

In an example, in response to initiating the PUCCH based BFR procedurethe wireless device may initiate a candidate beam identificationprocedure. For the candidate beam identification procedure, the wirelessdevice may identify the first RS. The first RS may be associated with aBFRQ resource of the one or more BFRQ resources. The BFRQ resource maycomprise at least one PUCCH (e.g. time and/or frequency) resource. In anexample, the wireless device may trigger the first request on the atleast one PUCCH resource.

In an example, the at least one PUCCH resource for an occasion of thefirst request (BFR Request in FIG. 21 ) may overlap with one or morePUCCH resources for transmission of one or more SRs (SR resource #1 andSR resource #2 in FIG. 21 ). In an example, when the at least one PUCCHresource for the occasion of the first request overlaps with one or morePUCCH resources for the transmission of the one or more SRs, thewireless device may drop (or delay or skip) the transmission of the oneor more SRs. In FIG. 21 , the wireless device may skip the transmissionof a first SR associated with SR resource #1 and a second SR associatedwith SR resource #2, and transmit the BFR request via the at least onePUCCH resource for the PUCCH-based BFR procedure.

In an example, a BFR procedure may have a higher priority than thetransmission of the one or more SRs. In an example, during the BFRprocedure of a serving cell, if the serving cell is used as a timingreference cell, inter symbol interference to other users may happen. Inan example, during the BFR procedure of a serving cell, if the servingcell is used as a pathloss reference cell, the wireless device may havean incorrect pathloss estimation. The incorrect pathloss estimation mayresult in interference to other users/cells.

Dropping the transmission of the one or more SRs, may, in an example,reduce an uplink interference to other wireless devices and/or cells.

In an example, the wireless device may perform a prioritization ruleamong one or more pending SRs and BFR request (if triggered). Theprioritization rule may be selecting, in order of high priority, 1) atransmission of the BFR request, 2) a first SR of the one or morepending SRs triggered by a logical channel with the highest priority, 3)a second SR of the one or more pending SRs triggered by a logicalchannel with the second highest priority and the like.

A wireless device may receive from a base station one or more messages.The one or more messages may comprise one or more configurationparameters. The one or more configuration parameters may indicate atleast: a beam failure instance counter, a scheduling request (SR)maximum counter and one or more physical uplink control channel (PUCCH)resources. In an example, the one or more PUCCH resources may beemployed for transmission of a signal indicating an SR.

In an example, the wireless device may initiate a beam failure recovery(BFR) procedure in response to a number of beam failure instanceindications reaching to the beam failure instance counter.

In an example, the wireless device may detect one or more pending SRs.The wireless device may transmit the signal via a PUCCH resource of theone or more PUCCH resources in response to the detecting the one or morepending SRs. The wireless device may increment an SR counter in responseto the transmitting the signal. In an example, the SR counter may reachto the SR maximum counter when the BFR procedure is ongoing. In anexample, in response to the SR counter reaching to the SR maximumcounter when the BFR procedure is ongoing, the wireless device may abortthe BFR procedure. In an example, the aborting the BFR procedure maycomprise resetting BFR timer (e.g., beamFailureRecoveryTimer) (ifconfigured), the first counter (e.g. signal transmission counter) and/ora first timer (e.g., ra-responsewindow), associated with the BFRprocedure. In an example, the BFR timer, the first counter and the firsttimer may be configured with the one or more configuration parameters.

In existing SR procedures, when a counter of SR transmissions (e.g.,SR_COUNTER) reaches to a maximum value (e.g., maximum number of SRtransmission, sr-TransMax), the wireless device may notify RRC torelease PUCCH for all serving cells and initiate a random accessprocedure and cancel all pending SRs.

When a similar SR procedure is implemented during an ongoing PUCCH-basedBFR procedure, when the counter of SR transmissions reaches to themaximum value, the wireless device may stop the ongoing PUCCH-based BFRprocedure. In an example, the stopping the ongoing PUCCH-based BFRprocedure may result in unsuccessful completion of the PUCCH-based BFRprocedure. In an example, the initiating the random-access procedure maydelay the recovery of beam failure between the base station and thewireless device. Implementation of existing procedures may beinefficient and may result in an increase in delay of the recovery ofthe beam failure.

In an example, a beam failure recovery procedure and an SR procedure maybe ongoing in the same TTI or slot or frame. In an example, a wirelessdevice may perform a transmission for a pending SR during an ongoing BFRprocedure. When the SR_COUNTER indicates a number equal to or greaterthan the maximum number of SR transmission, the wireless device mayabort the ongoing BFR procedure and initiate a random-access procedure.The aborting the ongoing BFR procedure may interrupt the ongoing BFRprocedure, which may result in a delay in recovering the beam failure.The aborting the ongoing BFR procedure may result in signaling overheadand/or latency.

In an example, a wireless device may initiate a BFR procedure based ondetecting a beam failure. The wireless device may detect the beamfailure based on the quality of downlink control channels of thewireless device being worse (e.g., higher BLER, lower SINR, lower RSRP,etc.) than a threshold. In an example, a base station may configure thewireless device with PUCCH resources for the BFR procedure. In anexample, a wireless device may have a pending SR for an uplink data(e.g., UL-SCH, transport block, etc.). In an example, the SR may betriggered during the (ongoing) BFR procedure. In an example, thewireless device may transmit an SR for the pending SR. The wirelessdevice may monitor, for an uplink grant, the downlink control channelsof the wireless device based on the transmitting the SR. The wirelessdevice may not receive the uplink grant via the downlink controlchannels with the beam failure. The wireless device may not receive theuplink grant via the downlink control channels based on detecting thebeam failure for the downlink control channels. This may result inretransmission of the (pending) SR. In an example, the number ofretransmissions of the (pending) SR may reach to a maximum configuredvalue. Based on the number of retransmissions of the (pending) SRreaching to the maximum configured value, the wireless device mayrelease the PUCCH resources for the BFR procedure and initiate arandom-access procedure. The wireless device may not transmit via thePUCCH resources for the BFR procedure based on the releasing. Thewireless device may abort the BFR procedure based on the releasing. Thismay result in unsuccessful completion of the BFR procedure. Therandom-access procedure to reestablish a link between the wirelessdevice and the base station may take a longer time the BFR procedure.There is a need to implement an enhanced procedure for the BFR of thewireless device.

Example embodiments implement an enhanced BFR procedure when the numberof retransmissions of the (pending) SR reaches a maximum configuredvalue during an ongoing BFR procedure. In an example embodiment, awireless device may not release the PUCCH resources when the number ofretransmissions of the (pending) SR reaches to a maximum configuredvalue during an ongoing BFR procedure. The wireless device may continuethe BFR procedure based on the not releasing the PUCCH resources.Continuing the BFR procedure may comprise the wireless devicetransmitting via the PUCCH resources for the BFR procedure based on notreleasing the PUCCH resources.

In an example embodiment, when the number of retransmissions of the(pending) SR reaches to the maximum configured value during an ongoingBFR procedure, a wireless device may suspend the pending SR until theBFR procedure is completed. The suspending of the pending SR maycomprise the wireless device not transmitting the pending SR until theBFR procedure is completed.

In an example embodiment, when the number of retransmissions of the(pending) SR reaches to the maximum configured value during an ongoingBFR procedure, a wireless device may reset the number of retransmissionsof the (pending) SR to a first value (e.g., zero).

This enhanced process improves downlink control signaling (e.g., thebase station may not need to reconfigure the released PUCCH resources)and reduces downlink signal overhead. The wireless device mayreestablish connection with the base station faster than therandom-access procedure.

FIG. 22 , FIG. 23 , FIG. 24 and FIG. 25 are examples of downlink beamfailure recovery procedure as per an aspect of an embodiment of thepresent disclosure.

In an example, a wireless device may receive one or more RRC messagecomprising parameters of one or more SR configurations and one or moreBFR configurations (time T0 in FIG. 22 -FIG. 25 ). In an example, foreach of the one or more SR configurations, the parameters may indicateat least one of: a SR prohibit timer; a maximum number of SRtransmission (e.g., MaxTrans in FIG. 22 -FIG. 25 ); a parameterindicating a periodicity and offset of SR transmission; and/or a PUCCHresource identified by a PUCCH resource index. In an example, when an SRof an SR configuration triggered (therefore in pending now) in responseto a BSR being triggered on an LCH corresponding to the SRconfiguration, a wireless device may initiate an SR procedure. In anexample, for the SR procedure, the wireless device may set a SR_COUNTER(e.g., SR counter in FIG. 22 -FIG. 25 ) to a first value (e.g., 0), ifthere is no other pending SRs corresponding to the SR configuration(time T1 in FIG. 22 -FIG. 25 ).

In an example, for the SR procedure, a wireless device may determinewhether there is at least one valid PUCCH resource for the pending SR atthe time of SR transmission occasion. If there is no valid PUCCHresource for the pending SR, the wireless device may initiate a randomaccess procedure on a PCell. The wireless device may cancel the pendingSR in response to no valid PUCCH resource for the pending SR.

In an example, if there is at least one valid PUCCH resource for thepending SR, a wireless device may determine an SR transmission occasionon the at least one valid PUCCH resource based on the periodicity andthe offset of SR transmission. In an example, if the SR prohibit timeris running, the wireless device may wait for another SR transmissionoccasion. In an example, if the SR prohibit timer is not running; and ifthe at least one valid PUCCH resource for the SR transmission occasiondoes not overlap with a measurement gap; and if the at least one validPUCCH resource for the SR transmission occasion does not overlap with anuplink shared channel (UL-SCH) resource; if the SR_COUNTER is less thanthe maximum number of SR transmission, the wireless device may incrementthe SR_COUNTER (e.g., by one), instruct the physical layer of thewireless device to signal the pending SR on the at least one valid PUCCHresource for the SR (time T2 in FIG. 22 -FIG. 25 ). The physical layerof the wireless device may transmit an uplink signal on the at least onevalid PUCCH resource for the pending SR. The wireless device may monitora PDCCH for detecting a DCI for uplink grant in response to transmittingthe PUCCH.

In an example, if a wireless device receives one or more uplink grantswhich may accommodate all pending data available for transmission, thewireless device may cancel the pending SR, and/or stop the SR prohibittimer. The wireless device may complete the SR procedure successfully inresponse to the receiving the one or more uplink grants.

In an example, if the wireless device does not receive one or moreuplink grants which may accommodate all pending data available fortransmission, the wireless device may repeat one or more actionscomprising: determining the at least one valid PUCCH resource; checkingwhether the SR prohibit timer is running; whether the SR_COUNTER isequal or greater than the maximum number of SR transmission;incrementing the SR_COUNTER, transmitting the SR and starting the SRprohibit timer; monitoring a PDCCH for uplink grant.

In an example, a wireless device may initiate or perform a PUCCH-basedbeam failure recovery (BFR) procedure during an SR procedure (timebetween T1 and T3 in FIG. 22 -FIG. 25 ). In an example, a wirelessdevice may perform a PUCCH-based beam failure recovery (BFR) procedurewhen an SR procedure is completed unsuccessfully (time T3 in FIG. 22-FIG. 25 ). In an example, the SR procedure may be completedunsuccessfully when the SR_COUNTER indicates a number equal to orgreater than the maximum number of SR transmission.

In an example, if the SR_COUNTER indicates a number equal to or greaterthan the maximum number of SR transmission (time T3 in FIG. 22 -FIG. 25), a wireless device may complete the SR procedure unsuccessfully. Inresponse to the completing the SR procedure unsuccessfully, if there isno ongoing beam failure recovery procedure (e.g., PUCCH-based BFR orPRACH based BFR), the wireless device may release PUCCH for one or moreserving cells, and/or release SRS for the one or more serving cells,and/or clear one or more configured downlink assignments and uplinkgrants, and/or initiate a random-access procedure on a PCell, and/orcancel all the pending SRs.

In an example, in FIG. 22 , in response to the completing the SRprocedure unsuccessfully, if there is an ongoing beam failure recoveryprocedure (e.g., PUCCH-based BFR or PRACH based BFR), the wirelessdevice may keep performing the ongoing beam failure recovery procedure.In an example, the wireless device may not abort the ongoing beamfailure recovery procedure. In an example, the wireless device may notperform one or more actions comprising: releasing PUCCH for one or moreserving cells, and/or releasing SRS for the one or more serving cells,and/or clearing one or more configured downlink assignments and uplinkgrants, and/or initiating a random-access procedure on a PCell, and/orcanceling all the pending SRs.

In an example, in FIG. 22 , in response to the completing the SRprocedure unsuccessfully, if there is an ongoing beam failure recoveryprocedure (e.g., PUCCH-based BFR or PRACH based BFR), the wirelessdevice may keep performing the ongoing beam failure recovery procedure.In an example, the wireless device may not abort the ongoing beamfailure recovery procedure. In an example, the wireless device may notinitiate a random-access procedure on a PCell. In an example, thewireless device may cancel all the pending SRs.

In an example, in FIG. 23 , if the SR_COUNTER indicates a number equalto or greater than the maximum number of SR transmission (time T3), awireless device may complete the SR procedure unsuccessfully. Inresponse to the completing the SR procedure unsuccessfully, if there isan ongoing beam failure recovery procedure (e.g., PUCCH-based BFR orPRACH based BFR), the wireless device may abort the ongoing beam failurerecovery procedure, release PUCCH for one or more serving cells, and/orrelease SRS for the one or more serving cells, and/or clear one or moreconfigured downlink assignments and uplink grants, and/or initiate arandom-access procedure on a PCell, and/or cancel all the pending SRs.In an example, the aborting the ongoing beam failure recovery maycomprise cancelling the first request, the resetting the BFR timer, thefirst counter and/or the first timer associated with the ongoing beamfailure recovery procedure.

In an example, in FIG. 24 , in response to the completing the SRprocedure unsuccessfully, if there is an ongoing beam failure recoveryprocedure (e.g., PUCCH-based BFR or PRACH based BFR), the wirelessdevice may keep performing the ongoing beam failure recovery procedure.In an example, the wireless device may not abort the ongoing beamfailure recovery procedure. In an example, the wireless device may notinitiate a random-access procedure on a PCell. In an example, thewireless device may suspend all the pending SRs until the ongoing beamfailure recovery procedure is completed (e.g., successfully). In anexample, the wireless device may not perform an uplink transmission forthe all the pending SRs until the ongoing beam failure recoveryprocedure is completed.

In an example, in FIG. 25 , in response to the completing the SRprocedure unsuccessfully, if there is an ongoing beam failure recoveryprocedure (e.g., PUCCH-based BFR or PRACH based BFR), the wirelessdevice may keep performing the ongoing beam failure recovery procedure.In an example, the wireless device may not abort the ongoing beamfailure recovery procedure. In an example, the wireless device may notinitiate a random-access procedure on a PCell or release PUCCH for oneor more serving cells, and/or release SRS for the one or more servingcells, and/or clear one or more configured downlink assignments anduplink grants. In an example, the wireless device may reset theSR_COUNTER to zero.

In an example, if the SR_COUNTER indicates a number equal to or greaterthan the maximum number of SR transmission (time T3 in FIG. 22 -FIG. 25), a wireless device may complete the SR procedure unsuccessfully. Inresponse to the completing the SR procedure unsuccessfully, if there isan ongoing beam failure recovery procedure (e.g., PUCCH-based BFR orPRACH based BFR), it is a UE implementation to abort the ongoing beamfailure recovery procedure and initiate a random access procedure orkeep performing the ongoing beam failure recovery procedure and notinitiate a random-access procedure.

FIG. 26 , FIG. 27 , and FIG. 28 are examples of downlink beam failurerecovery procedure as per an aspect of an embodiment of the presentdisclosure.

In an example, a wireless device may receive one or more RRC messagecomprising parameters of one or more SR configurations and one or moreBFR configurations (time T0 in FIG. 26 -FIG. 28 ). In an example, foreach of the one or more SR configurations, the parameters may indicateat least one of: a SR prohibit timer; a maximum number of SRtransmission, a parameter indicating a periodicity and offset of SRtransmission; and/or a PUCCH resource identified by a PUCCH resourceindex. In an example, when an SR of an SR configuration triggered(therefore in pending now) in response to a BSR being triggered on anLCH corresponding to the SR configuration, a wireless device mayinitiate an SR procedure for a pending SR (time T1 in FIG. 26 -FIG. 28).

In an example, for the SR procedure, a wireless device may determinewhether there is at least one valid PUCCH resource for the pending SR atthe time of SR transmission occasion. If there is no valid PUCCHresource for the pending SR, the wireless device may initiate arandom-access procedure on a PCell. The wireless device may cancel thepending SR in response to there being no valid PUCCH resource for thepending SR.

In an example, a wireless device may initiate or perform a PUCCH-basedbeam failure recovery (BFR) procedure during an SR procedure (timebetween T1 and T2 in FIG. 26 -FIG. 28 ). In an example, a wirelessdevice may perform a PUCCH-based beam failure recovery (BFR) procedurewhen an SR procedure is completed unsuccessfully (time T2 in FIG. 26-FIG. 28 ). In an example, the SR procedure may be completedunsuccessfully when the wireless device cancels the pending SR inresponse to there being no valid PUCCH resource for the pending SR.

In an example, when the SR procedure is completed unsuccessfully inresponse to being no valid PUCCH resource for the pending SR, if thereis no ongoing beam failure recovery procedure (e.g., PUCCH-based BFR orPRACH based BFR), the wireless device may initiate a random-accessprocedure on a PCell and cancel the pending SR.

In an example, in FIG. 26 , when the SR procedure is completedunsuccessfully in response to being no valid PUCCH resource for thepending SR, if there is an ongoing beam failure recovery procedure(e.g., PUCCH-based BFR or PRACH based BFR), the wireless device may keepperforming the ongoing beam failure recovery procedure. In an example,the wireless device may not abort the ongoing beam failure recoveryprocedure. In an example, the wireless device may not perform one ormore actions comprising: initiating a random-access procedure on a PCelland cancelling the pending SR.

In an example, in FIG. 26 , when the SR procedure is completedunsuccessfully in response to being no valid PUCCH resource for thepending SR, if there is an ongoing beam failure recovery procedure(e.g., PUCCH-based BFR or PRACH based BFR), the wireless device may keepperforming the ongoing beam failure recovery procedure. In an example,the wireless device may not abort the ongoing beam failure recoveryprocedure. In an example, the wireless device may not perform initiate arandom-access procedure on a PCell. In an example, the wireless devicemay cancel the pending SR.

In an example, in FIG. 27 , when the SR procedure is completedunsuccessfully in response to being no valid PUCCH resource for thepending SR, if there is an ongoing beam failure recovery procedure(e.g., PUCCH-based BFR or PRACH based BFR), the wireless device mayabort the ongoing beam failure recovery procedure, initiate arandom-access procedure on a PCell and cancel the pending SR. In anexample, the aborting the ongoing beam failure recovery may comprisecancelling the first request (e.g., BFR request), the resetting the BFRtimer, the first counter and/or the first timer associated with theongoing beam failure recovery procedure.

In an example, in FIG. 28 , when the SR procedure is completedunsuccessfully in response to being no valid PUCCH resource for thepending SR, if there is an ongoing beam failure recovery procedure(e.g., PUCCH-based BFR or PRACH based BFR), the wireless device may keepperforming the ongoing beam failure recovery procedure. In an example,the wireless device may not abort the ongoing beam failure recoveryprocedure. In an example, the wireless device may not perform initiate arandom-access procedure on a PCell. In an example, the wireless devicemay suspend the pending SR until the ongoing beam failure recoveryprocedure is completed (e.g., successfully). In an example, the wirelessdevice may not perform an uplink transmission for the pending SR untilthe ongoing beam failure recovery procedure is completed.

In an example, when the SR procedure is completed unsuccessfully inresponse to being no valid PUCCH resource for the pending SR, if thereis an ongoing beam failure recovery procedure (e.g., PUCCH-based BFR orPRACH based BFR), it is a UE implementation to abort the ongoing beamfailure recovery procedure and initiate a random access procedure orkeep performing the ongoing beam failure recovery procedure and notinitiate a random-access procedure.

In an example, a wireless device may receive from a base station, one ormore messages. The one or more messages may comprise one or moreconfiguration parameters. The one or more configuration parameters mayindicate one or more first physical uplink control channel (PUCCH)resources. In an example, the one or more first PUCCH resources may beemployed for transmission of a first signal for a beam failure recoveryprocedure. In an example, the one or more configuration parameters mayfurther indicate one or more second PUCCH resources. In an example, theone or more second PUCCH resources may be employed for transmission of asecond signal for a scheduling request (SR).

In an example, the wireless device may initiate the beam failurerecovery procedure in response to a number of beam failure instanceindications reaching to the beam failure instance counter.

In an example, the wireless device may trigger the transmission of thefirst signal via a first PUCCH resource of the one or more first PUCCHresources in response to the initiating the beam failure recoveryprocedure. In an example, the first PUCCH resource may be associatedwith the selected RS.

In an example, the wireless device may detect one or more pending SRs.The wireless device may trigger the transmission of the second signalvia a second PUCCH resource of the one or more second PUCCH resources inresponse to the detecting the one or more pending SRs.

In an example, the wireless device may determine the first PUCCHresource overlapping at least partially in time (e.g., one or moresymbols, slots, etc.) with the second PUCCH resource.

In an example, in response to the determining, the wireless device maydrop (or skip) the transmission of the second signal and transmit thefirst signal via the first PUCCH resource. In an example, the dropping(or the skipping) may comprise transmitting the second signal in a nexttransmission opportunity in time. The next transmission opportunity maycomprise a third PUCCH resource of the one or more second PUCCHresources, wherein the third PUCCH resource does not overlap with thefirst PUCCH resource.

In an example, embodiment, a base station may configure a wirelessdevice with reference signals for a beam failure detection. In anexample, the wireless device may measure the reference signals for thebeam failure detection. In an example, the wireless device may provide abeam failure instance (BFI) indication to a MAC layer of the wirelessdevice based on the quality of the reference signals being worse (e.g.,higher BLER, lower RSRP, lower SINR) than a threshold. Based on the BFIindication, the MAC layer may increment a counter (e.g., BFI_COUNTER)and (re)start a timer (e.g., beamFailureDetectionTimer). When the timerexpires the wireless device may reset the counter (e.g., to zero). Whenthe counter reaches (e.g., equal to or greater than) to a configuredmaximum value (e.g., beamFailureInstanceMaxCount), the wireless devicemay initiate a BFR procedure.

In an example, the wireless device may transit into DRX inactive time(e.g., of DRX configuration). Measuring the reference signals in the DRXinactive time may increase the power consumption of the wireless device.In an example, initiating a BFR procedure in the DRX inactive time maywaste uplink resources (e.g., PUCCH, PRACH) of the BFR procedure. Thereis a need to implement an enhanced procedure for the BFR of the wirelessdevice.

In an example embodiment, the wireless device may stop measuring thereference signals in the DRX inactive time. This enhanced processreduces battery/power consumption at the wireless device. This enhancedprocess reduces the resource overhead for the BFR procedure (e.g., theuplink resources for the BFR procedure may not be configured for the DRXinactive time).

In an example, not measuring the reference signals in the DRX inactivetime may result in an expiry of the timer. The timer may expire beforetransitioning into the DRX active time (e.g., DRX period may be longerthan the timer). Not measuring the reference signals in the DRX inactivetime may result in an expiry of the timer earlier/prematurely. Resettingthe counter based on the expiry of the timer may delay the initiation ofthe BFR procedure. In an example, the wireless device may notinitiate/trigger the BFR procedure based on the expiry of the timer. Thewireless device may not recover/enhance the quality of the downlinkcontrol channels based on the delaying the initiation of the BFRprocedure. The wireless device may be less reactive/robust to beamfailures. There is a need to implement an enhanced procedure for the BFRof the wireless device.

In example embodiment, the wireless device may not reset the counter inthe DRX inactive time. The wireless device may ignore the BFI indicationin the DRX inactive time. The wireless device may not reset the counterin the DRX inactive time. The wireless device may stop the timer basedon the transiting into DRX inactive time and restart the timer based onthe transiting into DRX active time. This enhanced process improvesrobustness of the wireless device to the beam failures. In an example,the wireless device may react/initiate a BFR procedure faster/earlierand recover downlink control signaling in a timely manner.

FIG. 29 shows an example of beam failure indication. In an example, awireless device may use at least one UE variable for a beam failuredetection. BFI_COUNTER may be one of the at least one UE variable. TheBFI_COUNTER may be a counter for a beam failure instance indication. TheBFI_COUNTER may be initially set to zero.

In an example, if a MAC entity of a wireless device receives a beamfailure instance indication from a lower layer (e.g. PHY) of thewireless device, the wireless device may start or restartbeamFailureDetectionTimer (e.g., BFR timer in FIG. 29 ). In addition tostarting or restarting the beamFailureDetectionTimer, the wirelessdevice may increment BFI_COUNTER by one (e.g., at time T, 2T, 5T in FIG.29 ). In an example, the wireless device may initiate a random accessprocedure (e.g. on an SpCell) for a beam failure recovery and start thebeamFailureRecoveryTimer (if configured) in response to the BFI_COUNTERbeing greater than or equal to beamFailureInstanceMaxCount and beingconfigured with beamFailureRecoveryConfig via RRC signaling. In anexample, in FIG. 29 , the wireless device may initiate the random accessprocedure at time 6T, when the beamFailureInstanceMaxCount (e.g., 3) isreached. The wireless device may apply the one or more parameters (e.g.,powerRampingStep, preambleReceivedTargetPower, and preambleTransMax) inthe BeamFailureRecoveryConfig in response to the initiating the randomaccess procedure. In an example, the random access procedure may becontention-free random access. In an example, if the random accessprocedure is successfully completed, the wireless device may considerthe beam failure recovery procedure successfully completed. In anexample, the wireless device may stop the beamFailureRecoveryTimer (ifconfigured) in response to the random access procedure beingsuccessfully completed.

In an example, the wireless device may initiate a contention-basedrandom access procedure (e.g. on an SpCell) in response to theBFI_COUNTER being greater than or equal to beamFailureInstanceMaxCountand not being configured with beamFailureRecoveryConfig via RRCsignaling. In an example, if the contention-based random accessprocedure is successfully completed, the wireless device may considerthe beam failure recovery procedure successfully completed.

In an example, if the beamFailureDetectionTimer expires, the wirelessdevice may set the BFI_COUNTER to zero (e.g., in FIG. 29 , between time3T and 4T).

In an example, for a BWP switching, a transition time may be necessaryfor a wireless device for processing time and RF tuning time. A wirelessdevice may not receive one or more downlink signals during thetransition time of the BWP switching (e.g., UL BWP switching or DL BWPswitching, or both). A wireless device may not transmit one or moreuplink signals during the transition time of the BWP switching (e.g., ULBWP switching or DL BWP switching, or both). In an example, a transitiontime of a BWP switching may depend on at least one of changing a centerfrequency of an active BWP; or changing a bandwidth of an active BWP; orchanging a center frequency of an active BWP and changing a bandwidth ofthe active BWP; or changing a numerology (e.g., subcarrier spacing) ofan active BWP without changing a center frequency and a bandwidth of theactive BWP.

In an example, for a DCI-based BWP switching, a transition time of anactive DL and/or active UL BWP switch is a time duration from a PDCCHreception carrying a DCI indicating the active DL BWP and/or UL BWPswitch until the beginning of a slot indicated by a first number (e.g.,4, 8, 20, 32 slots or symbols). In an example, the transition time maybe 2 msec. In an example, the first number may be indicated in the DCI.

In an example, a wireless device, during a measurement gap, may notperform the transmission of HARQ feedback, SR and CSI; may not reportSRS; may not transmit UL-SCH, except for Msg3 used in contention-basedrandom-access procedure. In an example, the wireless device may notmonitor at least one PDCCH when the ra-ResponseWindow or thera-ContentionResolutionTimer is running.

In an example, when a wireless device is configured with a discontinuousreception (DRX) operation, the wireless device, in RRC_CONNECTED, maymonitor the PDCCH discontinuously. RRC may control the DRX operation byconfiguring at least one or more parameters comprisingdrx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDLor drx-RetransmissionTimerUL.

In an example, when the wireless device is not in Active time (e.g., DRXinactive time), the wireless device may not monitor the PDCCH. TheActive time may include a time while drx-onDurationTimer ordrx-InactivityTimer or drx-RetransmissionTimerDL ordrx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running, ora scheduling request is sent on PUCCH and is pending; or a PDCCHindicating a new transmission addressed to the C-RNTI of the wirelessdevice has not been received after successful reception of a randomaccess response for a random access preamble not selected by thewireless device among contention-based random access preamble.

In an example, a physical layer of the wireless device may not send abeam failure indication (BFI) to a MAC layer of the wireless device whenthe wireless device is not monitoring PDCCH. In an example, if awireless device is configured with DRX operation, a physical layer ofthe wireless device may not send a beam failure indication (BFI) to aMAC layer of the wireless device when the wireless device is not in theActive time (e.g., DRX inactive time). In an example, a physical layerof the wireless device may not send a beam failure indication (BFI) to aMAC layer of the wireless device when the wireless device is in ameasurement gap. In an example, a physical layer of the wireless devicemay not send a beam failure indication (BFI) to a MAC layer of thewireless device during a BWP switching.

In an example, a physical layer of a wireless device may provide a beamfailure indication (e.g., BFI) to higher layers (e.g. MAC) when a radiolink quality (e.g., BLER, L1-RSRP) of one or more RSs (e.g., periodicCSI-RS, SSB) is worse than a first threshold. In an example, the one ormore RSs may be configured by a base station via RRC signaling. In anexample, the first threshold may be configured by a higher layer (e.g.,RRC, MAC). In an example, the wireless device may provide the beamfailure indication to the higher layers with a periodicity. Theperiodicity may be determined by a maximum between the shortestperiodicity of the one or more RSs and a second value (e.g. 2 msec). Inan example, the second value may be configured by higher layers (e.g.,RRC).

FIG. 30 shows an example of a BFI when a wireless device does notmonitor the PDCCH. In an example, at time T_(a), the wireless device mayinitiate a BWP switching. In an example, the BWP switching may betriggered by a DCI (e.g., DCI-based BWP switching) or an expiry of aninactivity timer. In an example, at time T_(a), the wireless device maystart DRX inactive time. In an example, at time T_(a), the wirelessdevice may start a measurement gap. In an example, a time duration maycomprise a duration of time the wireless device does not monitor PDCCH.The wireless device may not receive one or more downlink signals duringthe time duration of the BWP switching or time duration of themeasurement gap or time duration of the DRX inactive time (e.g., betweenT_(a) and T_(b) in FIG. 30 ). The wireless device may not assess a radiolink quality (e.g., BLER, L1-RSRP) for one or more RSs (e.g., periodicCSI-RS, SSB) during the time duration (e.g., between T_(a) and T_(b) inFIG. 30 ). In an example, an instance of the beam failure indication maybe within the time duration (e.g., 3T₁ in FIG. 30 ).

In an example, in the time duration, the wireless device may not assessa radio link quality of the one or more RSs. In an example, in the timeduration, the wireless device may assess a radio link quality of asubset of the one or more RSs. In that case, the instance of the beamfailure indication may not be reliable.

In an example, in response to not assessing the radio link quality, thewireless device may not provide a beam failure indication at theinstance of the beam failure indication (e.g., at 3T₁ in FIG. 30 )within the time duration. In an example, a beam failure detection timermay expire in response to not receiving the beam failure indicationduring the time duration (e.g., between 3T1 and T_(b) in FIG. 30 ). Thebeam failure detection timer may start or restart in response toreceiving a beam failure indication. In an example, the wireless devicemay set a beam failure counter (e.g., BFI_COUNTER) to zero in responseto the beam failure detection timer expiring during the time duration.In that case, an initiation of a beam failure recovery procedure may bedelayed. For example, in FIG. 30 , the beam failure recovery may beinitiated at time 3T2 instead of 3T₁. In an example, the one or more RSsmay have lower radio link quality than the first threshold during theBWP transition time. In that case, not receiving the beam failureindication during the transition time may not reflect a true radio linkquality of one or more downlink control channels associated (QCLed) withthe one or more RSs.

In an example, the wireless device may provide a beam failure indicationto higher layers within the time duration (e.g., DRX inactive time,measurement gap, BWP switching). In an example, the beam failureindication within the time duration may be same as a previous beamfailure indication. In an example, in FIG. 30 , within time duration, aninstance of a beam failure indication may exist (e.g., at time 3T1). Inan example, the wireless device may provide a beam failure indication tothe higher layers within time duration (e.g., at time 3T1) if a beamfailure indication was provided in the previous instance (e.g., at time2T1). In an example, the wireless device may not provide a beam failureindication to the higher layers within the time duration (e.g., at time3T1) if the beam failure indication was not provided in the previousinstance (e.g., at time 2T1). This may enable a beam failure counter notto reset during the BWP transition time. In an example, the notresetting the beam failure counter during the BWP transition time mayresult in a faster BFR procedure. In an example, the beam failurecounter may reach to the beamFailureInstanceMaxCount faster. In anexample, in response to the beam failure counter being equal to thebeamFailureInstanceMaxCount, the wireless device may initiate a randomaccess procedure for a beam failure. In that case, the wireless devicemay avoid RLF.

In an example, a physical layer of the wireless device may not send abeam failure indication (BFI) to a MAC layer of the wireless deviceduring the time duration (e.g., DRX inactive time, measurement gap, BWPswitching). In an example, the beam failure timer (e.g.,beamFailureDetectionTimer) may not be reset or stopped during the timeduration. In an example, the beam failure timer may not be reset orstopped when the time duration starts (e.g., Ta in FIG. 30 ). In anexample, when the beamFailureDetectionTimer expires during the timeduration, the wireless device may not set the beam failure counter(e.g., BFI_COUNTER) to zero.

In an example, a physical layer of the wireless device may not send abeam failure indication (BFI) to a MAC layer of the wireless deviceduring the time duration (e.g., DRX inactive time, measurement gap, BWPswitching). In an example, the beam failure timer (e.g.,beamFailureDetectionTimer) may be reset or stopped when the timeduration starts (e.g., Ta in FIG. 30 ). In an example, the beam failuretimer may not run during the time duration. The resetting the beamfailure timer may avoid resetting the beam failure counter (e.g.,BFI_COUNTER) to zero.

In an example, the wireless device may restart the beam failure timer(e.g., beamFailureDetectionTimer) when the time duration ends (e.g., Tbin FIG. 30 ). In an example, the wireless device may restart the beamfailure timer (e.g., beamFailureDetectionTimer) with a first BFI outsideof the time duration (e.g., Tb in FIG. 30 ).

In an example, in response to starting the time duration, the wirelessdevice may restart the beam failure timer. This may enable the beamfailure counter not to reset to zero during the time duration. In anexample, in response to the restarting the beam failure timer, thewireless device may not provide a beam failure indication to a higherlayer (e.g., MAC) during the BWP transition time.

In an example, in response to starting the time duration, the wirelessdevice may restart the beam failure timer. This may enable the beamfailure counter not to reset to zero during the time duration. In anexample, in response to the restarting the beam failure timer, thewireless device may provide a beam failure indication to a higher layer(e.g., MAC) during the time duration if the wireless device may monitora subset of the one or more RSs before the time duration starts (e.g.,between time 2T1 and Ta in FIG. 30 ).

In an example, the wireless device may provide a beam failure indicationto a higher layer (e.g., MAC) during the time duration if the wirelessdevice may monitor a subset of the one or more RSs during a second timeduration between a previous instance of beam failure indication and theinitiation of the time duration (e.g., between time 2T₁ and T_(a) inFIG. 30 ). If at least one of the subset of the one or more RSs has aradio link quality higher than a first threshold (e.g., low BLER, highSINR, etc.), the wireless device may not provide a beam failureindication to the higher layers. Otherwise, the wireless device mayprovide a beam failure indication to the higher layers. In an example,the beam failure indication timer may not be reset and/or stopped inresponse to starting the time duration.

In an example, the wireless device may always provide a beam failureindication to a higher layer (e.g., MAC) during the time duration. Thismay enable the beam failure counter not to reset to zero during the timeduration. In an example, the beam failure indication timer may not bereset and/or stopped in response to starting the time duration.

In an example, a timing advance group (TAG) containing an SpCell of awireless device may be referred to as primary timing advance group(PTAG). In an example, a secondary timing advance group (STAG) may referto other TAGs (e.g., any TAG other than PTAG).

In an example, RRC may configure, a wireless device, with a timealignment timer per TAG. The time alignment timer may be used formaintenance of uplink time alignment. In an example, one or more servingcells of the wireless device may belong to a TAG. The time alignmenttimer may control how long the one or more serving cells belonging tothe TAG are uplink time aligned.

In an example, a time alignment timer may be associated with a TAG. Inan example, a serving cell may belong to the TAG. In an example, thewireless device may not perform an uplink transmission, except a randomaccess preamble transmission, on the serving cell when the timealignment timer is not running.

In an example, a time alignment timer may be associated with a PTAG.When the time alignment timer is not running, the wireless device maynot perform an uplink transmission on any serving cell (e.g., associatedwith PTAG or STAG), except the random access preamble transmission onthe SpCell.

In an example, in response to detecting a beam failure, a wirelessdevice may initiate a PUCCH-based beam failure recovery (BFR) procedureof a cell. In an example, the cell may be SpCell (e.g., PCell). In anexample, the wireless device may be configured with a time alignmenttimer associated with a TAG (e.g., PTAG). In an example, the cell maybelong to the TAG.

In an example, if the time alignment timer expires during thePUCCH-based BFR procedure of the cell, the wireless device may abort thePUCCH-based BFR procedure. In an example, in response to the abortingthe PUCCH-based BFR procedure, the wireless device may initiate arandom-access procedure (e.g., on SpCell).

In an example, in response to the aborting the PUCCH-based BFRprocedure, the wireless device may at least: reset a BFR timer (e.g.,BFR timer in FIG. 20 ), reset a first counter (BFR counter in FIG. 20 ),or reset a first timer (e.g., Response window in FIG. 20 ).

In an example, if the time alignment timer expires during thePUCCH-based BFR procedure of the cell, the wireless device may not abortthe PUCCH-based BFR procedure.

In an example, in response to detecting a beam failure, a wirelessdevice may initiate a beam failure recovery (BFR) procedure of a cell.In an example, the BFR procedure may be PUCCH-based BFR procedure. In anexample, the BFR procedure may be PRACH-based BFR procedure. In anexample, the cell may be SCell. In an example, the wireless device maybe configured with a time alignment timer associated with a TAG (e.g.,STAG, PTAG). The cell may belong to the TAG.

In an example, if the time alignment timer expires during the BFRprocedure of the cell, the wireless device may abort the BFR procedure.In an example, in response to the aborting the BFR procedure, thewireless device may initiate a random-access procedure (e.g., onSpCell).

In an example, in response to the aborting the BFR procedure, thewireless device may at least: reset a BFR timer (e.g., BFR timer in FIG.20 or beamFailureRecoveryTimer), reset a first counter (BFR counter inFIG. 20 or PREAMBLE TRANSMISSION COUNTER), or reset a first timer (e.g.,Response window in FIG. 20 or ra-ResponseWindow).

In an example, if the time alignment timer expires during the BFRprocedure of the cell, the wireless device may not abort the BFRprocedure.

In an example, in response to the aborting the PUCCH-based BFRprocedure, the wireless device may at least: reset the BFR timer (e.g.,BFR timer in FIG. 20 ), reset the first counter (BFR counter in FIG. 20), or reset the first timer (e.g., Response window in FIG. 20 ).

In an example, if BWP-InactivityTimer is configured, for an SCell, ifthe Default-DL-BWP is configured, and the active DL BWP is not the BWPindicated by the Default-DL-BWP; or if the Default-DL-BWP is notconfigured, and the active DL BWP is not the initial BWP: if RandomAccess procedure is initiated, the MAC entity may not stop theBWP-InactivityTimer associated with the active DL BWP of the activatedServing Cell. The wireless device may stop a second BWP-InactivityTimerassociated with a second active DL BWP of an SpCell.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 31 and FIG. 32 are example flow diagrams as per an aspects ofembodiments of the present disclosure. At 3110, a wireless device mayreceive one or more messages. The one or more messages may comprise oneor more configuration parameters. The one or more configurationparameters may indicate one or more reference signals for a beam failuredetection procedure. The one or more configuration parameters mayindicate a discontinuous reception (DRX) configuration for controllingtransitions between a DRX inactive state and a DRX active state. At3120, the beam failure detection procedure may be performed based onmeasurements of the one or more reference signals. At 3140, a firstvalue of a counter may be determining based on detecting at least onebeam failure instance during the DRX active state (3130). At 3150, basedon the DRX configuration, a transition from the DRX active state to theDRX inactive state may occur. At 3160, the beam failure detectionprocedure may be stopped in response to the transitioning. At 3170,after transitioning from the DRX inactive state to the DRX active state,the beam failure detection procedure may continue to perform with thefirst value of the counter.

According to an example embodiment, the one or more configurationparameters may further indicate a beam failure detection timer.According to an example embodiment, at 3210, the beam failure detectiontimer may be stopped based on transitioning from the DRX active state tothe DRX inactive state. According to an example embodiment, at 3220, thebeam failure detection timer may be restarted based on transitioningfrom the DRX inactive state to the DRX active state. According to anexample embodiment, at 3230, the beam failure detection timer may berestarted based on transitioning from the DRX active state to the DRXinactive state. According to an example embodiment, at 3240, the firstvalue of the counter not be reset to zero based on an expiry of the beamfailure detection timer in the DRX inactive state.

According to an example embodiment, the beam failure detection timer maybe restarted based on the detecting the at least one beam failureinstance. According to an example embodiment, the first value of thecounter may be reset to zero based on an expiry of the beam failuredetection timer in the DRX active state. According to an exampleembodiment, the beam failure detection procedure stopping may comprisenot providing a beam failure instance indication, by a physical layer ofthe wireless device, to a medium-access control layer of the wirelessdevice. According to an example embodiment, the beam failure detectionprocedure may comprise assessing a radio link quality of the one or morereference signals. According to an example embodiment, the detecting atleast one beam failure instance may comprise assessing the radio linkquality of the one or more reference signals lower than a threshold.According to an example embodiment, the one or more configurationparameters may indicate the threshold. According to an exampleembodiment, the threshold may be based on a hypothetical block errorrate. According to an example embodiment, the stopping the beam failuredetection procedure may comprise not assessing a radio link quality ofthe one or more reference signals.

According to an example embodiment, at 3250, a beam failure instanceindication in the DRX inactive state may be provided by a physical layerof the wireless device to a medium-access control layer of the wirelessdevice. The beam failure instance indication may be the same as aprevious beam failure instance indication. According to an exampleembodiment, a beam failure instance indication may be provided by aphysical layer of the wireless device to a medium-access control layerof the wireless device in the DRX inactive state. According to anexample embodiment, the one or more configuration parameters mayindicate a beam failure instance counter. According to an exampleembodiment, a beam failure recovery procedure may be initiated based onthe first value of the counter being equal to or greater than the beamfailure instance counter. According to an example embodiment, the one ormore reference signals may comprise one or more channel stateinformation RSs. According to an example embodiment, the one or morereference signals may comprise one or more synchronizationsignal/physical broadcast channel blocks.

FIG. 33 and FIG. 34 are example flow diagrams as per an aspects ofembodiments of the present disclosure. At 3310, a wireless device mayreceive one or more messages. The one or messages may comprise one ormore configuration parameters. The one or more configuration parametersmay indicate one or more physical uplink control channel (PUCCH)resources. The one or more configuration parameters may indicate athreshold for a scheduling request (SR) transmission. At 3320, an uplinksignal may be transmitted via a PUCCH resource of the one or more PUCCHresources, based on initiating a beam failure recovery (BFR) procedure.At 3340, while BFR procedure is ongoing (3330), a number of SRtransmissions exceeding the threshold may be determined. At 3350, basedon the determining, the one or more PUCCH resources may not be released.At 3360, transmission may occur via the PUCCH resource of the one ormore PUCCH resources for the BFR procedure.

According to an example embodiment, at 3410, the BFR procedure maycontinue based on the determining. According to an example embodiment,the transmitting via the PUCCH resource may comprise the transmittingvia the PUCCH resource based on the continuing the BFR procedure.According to an example embodiment, one or more sound reference signalsmay not be released based on the determining. According to an exampleembodiment, one or more configured uplink grants may not be releasedbased on the determining. According to an example embodiment, one ormore configured downlink assignments may not be released based on thedetermining. According to an example embodiment, at 3420, arandom-access procedure may be not initiating based on the determining.

According to an example embodiment, at 3430, the number of SRtransmissions for one or more pending SRs may be performed. According toan example embodiment, at 3440, the one or more pending SRs may not becancelled based on the determining. According to an example embodiment,at 3450, based on the determining, one or more pending SRs may besuspended until the BFR procedure is completed.

According to an example embodiment, the suspending the one or morepending SRs may comprise not transmitting an uplink signal for the oneor more pending SRs until the BFR procedure is completed. According toan example embodiment, a response window may be started based on thetransmitting the uplink signal. According to an example embodiment, abeam failure counter may be incremented based on the transmitting theuplink signal.

According to an example embodiment, at 3460, based on the determining,the BFR procedure may not abort. According to an example embodiment, at3470, based on the determining, the number of SR transmissions may bereset to zero. According to an example embodiment, at 3480, based on thedetermining, the BFR procedure may abort. According to an exampleembodiment, the BFR procedure aborting may comprise resetting a beamfailure counter. According to an example embodiment, the BFR procedureaborting may comprise resetting a response window. According to anexample embodiment, based on the initiating the BFR procedure, a beamfailure recovery timer may be started. According to an exampleembodiment, the BFR procedure aborting may comprise resetting the beamfailure recovery timer. According to an example embodiment, the BFRprocedure initiating may comprise initiating the BFR procedure based ona first request. According to an example embodiment, the first requestmay trigger based on a beam failure detection. According to an exampleembodiment, the BFR procedure aborting may comprise cancelling the firstrequest.

FIG. 35 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3510, a wireless device may receive one ormore messages. The one or more messages may comprise one or moreconfiguration parameters. The one or more configuration parameters mayindicate one or more physical uplink control channel (PUCCH) resources.At 3530, a scheduling request (SR) procedure may be initiated based ondetecting one or more pending SRs (3520). At 3540, a beam failurerecovery (BFR) procedure may be initiated. The SR procedure may notsuccessfully complete. At 3550, a determination may be made that the BFRprocedure is ongoing when the SR procedure unsuccessfully completes. At3560, based on the determining, the one or more PUCCH resources may notbe released. At 3570, a transmission may occur via a PUCCH resource ofthe one or more PUCCH resources for the BFR procedure.

FIG. 36 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 3610, a wireless device may receive one ormore messages. The one or more messages may comprise one or moreconfiguration parameters. The one or more configuration parameters mayindicate one or more first physical uplink control channel (PUCCH)resources for transmission of a first signal for a beam failure recoveryprocedure. The one or more configuration parameters may indicate one ormore second PUCCH resources for transmission of a second signal for ascheduling request (SR). In response to initiating the beam failurerecovery procedure (3620), the transmission of the first signal via afirst PUCCH resource of the one or more first PUCCH resources may betriggered at 3630. In response to one or more pending SRs (3640), thetransmission of the second signal via a second PUCCH resource of the oneor more second PUCCH resources may be triggered at 3650. At 3660, adetermination may be made that the first PUCCH resource overlaps, atleast partially in time, with the second PUCCH resource. At 3670, thetransmission of the second signal may be dropped. At 3680, the firstsignal may be performed via the first PUCCH resource.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A wireless device comprising: a communicationinterface configured to receive one or more messages comprising one ormore configuration parameters indicating: one or more reference signalsfor a beam failure detection procedure; and a discontinuous reception(DRX) configuration for controlling transitions between a DRX inactivestate and a DRX active state; processor circuitry configured to: performthe beam failure detection procedure based on measurements of the one ormore reference signals; increment, in the DRX active state, a counter ofdetected beam failure instances to a first value of the counter during atime period of a beam failure detection timer; transition from the DRXactive state to the DRX inactive state based on the DRX configuration;in response to the transitioning from the DRX active state to the DRXinactive state and during the DRX inactive state spanning a plurality oftime periods of the beam failure detection timer: stop the measurementsof the one or more reference signals for the beam failure detectionprocedure; and retain the first value of the counter; and continue toperform the beam failure detection procedure with the first value of thecounter after transitioning from the DRX inactive state to the DRXactive state.
 2. The wireless device of claim 1, wherein the one or moreconfiguration parameters further indicate the beam failure detectiontimer.
 3. The wireless device of claim 2, wherein the processorcircuitry is further configured to stop the beam failure detection timerbased on transitioning from the DRX active state to the DRX inactivestate.
 4. The wireless device of claim 2, wherein the processorcircuitry is further configured to restart the beam failure detectiontimer based on transitioning from the DRX inactive state to the DRXactive state.
 5. The wireless device of claim 2, wherein the processorcircuitry is further configured to restart the beam failure detectiontimer based on transitioning from the DRX active state to the DRXinactive state.
 6. The wireless device of claim 2, wherein the processorcircuitry is further configured not to reset, during the DRX inactivestate, the first value of the counter to zero based on an expiry of thebeam failure detection timer in the DRX inactive state.
 7. The wirelessdevice of claim 2, wherein the processor circuitry is further configuredto restart the beam failure detection timer based on detecting at leastone beam failure instance.
 8. The wireless device of claim 2, whereinthe processor circuitry is further configured to reset the first valueof the counter to zero based on an expiry of the beam failure detectiontimer in the DRX active state.
 9. The wireless device of claim 1,wherein the processor circuitry is configured to stop the beam failuredetection procedure by not providing a beam failure instance indication,by a physical layer of the wireless device, to a medium-access controllayer of the wireless device.
 10. The wireless device of claim 1,wherein the processor circuitry is configured to perform the beamfailure detection procedure by assessing a radio link quality of the oneor more reference signals.
 11. The wireless device of claim 10, whereinthe processor circuitry is configured to detect at least one beamfailure instance by assessing the radio link quality of the one or morereference signals lower than a threshold.
 12. The wireless device ofclaim 11, wherein the one or more configuration parameters indicate thethreshold.
 13. The wireless device of claim 11, wherein the threshold isbased on a hypothetical block error rate.
 14. The wireless device ofclaim 11, wherein the processor circuitry is configured to stop the beamfailure detection procedure by not assessing a radio link quality of theone or more reference signals.
 15. The wireless device of claim 11,wherein the processor circuitry is further configured to provide a beamfailure instance indication in the DRX inactive state, by a physicallayer of the wireless device to a medium-access control layer of thewireless device, wherein the beam failure instance indication is thesame as a previous beam failure instance indication.
 16. The wirelessdevice of claim 11, wherein the processor circuitry is furtherconfigured to provide a beam failure instance indication, by a physicallayer of the wireless device, to a medium-access control layer of thewireless device in the DRX inactive state.
 17. The wireless device ofclaim 11, wherein the one or more configuration parameters furtherindicate the counter of beam failure instances.
 18. The wireless deviceof claim 17, wherein the processor circuitry is further configured toinitiate a beam failure recovery procedure based on the first value ofthe counter being equal to or greater than the counter of beam failureinstances.
 19. The wireless device of claim 11, wherein the one or morereference signals comprise one or more channel state informationreference signals.
 20. The wireless device of claim 11, wherein the oneor more reference signals comprise one or more synchronizationsignal/physical broadcast channel blocks.